check_context

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations provided, the description carries the full behavioral burden and does so well. It explicitly declares 'READ OPERATION - No confirmation needed. Safe to call freely,' and it discloses the return behavior: a simple yes/no with finding count and top topics. This is valuable transparency beyond the schema.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is well-organized and front-loaded with the core purpose, followed by useful sections for triggers, workflow, safety, parameters, and returns. Minor redundancy exists between 'AUTOMATIC TRIGGERS' and 'WORKFLOW POSITION,' both saying to call at the start of a task, but overall the structure is effective.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple two-parameter convenience tool with no output schema, the description is complete: it explains when to call it, what it returns, how to supply parameters, and that it is safe. An agent has enough information to invoke it correctly in the intended workflow.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0%, so the description must compensate for the lack of parameter documentation. It does provide meaningful semantics for both parameters: query is 'What you're about to work on' and project is 'Filter by project (optional).' The explanations are brief but sufficient for an agent to understand each parameter's role.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states a specific action and resource: 'Quick check if relevant context exists before starting work' and 'returns a simple yes/no with relevant finding count and top topics.' It also differentiates itself from related tools by identifying itself as a convenience wrapper around search_fts, so an agent understands its narrow scope.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description gives explicit when-to-use guidance: 'Call this at the start of ANY new task' and 'WORKFLOW POSITION: First tool to call when starting any task.' It does not explicitly state when not to use it or name alternative tools, but the simple yes/no return format implies when a more detailed search is needed.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.