search_context_items

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

With no annotations provided, the description must carry the full behavioral burden. It notes that matching items are returned but does not clarify whether the operation is read-only, whether the path parameter is required or defaults to something, or what 'details' includes. No side effects, permissions, or return format are disclosed.

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 a single concise sentence that immediately conveys the tool's purpose and mentions the key parameters. No filler or redundant information.

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?

Without an output schema, the description should clarify return values, but it only says 'Returns matching items with their details.' It does not address edge cases like empty query/tags (potentially listing all), pagination, or the exact structure of the returned items. This is adequate for a simple search tool but leaves some gaps.

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 100%, so each parameter has a description. The tool description mentions query and tags, reinforcing their purpose, but path and showCompleted are only explained by the schema. The baseline of 3 is appropriate since the schema does the heavy lifting, with some added context for two parameters.

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 the tool searches context items using a query string and/or tags, which is a specific verb+resource+scope. It implicitly distinguishes from list_context_items by adding search criteria and from mutation tools like add/remove/edit.

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 implies the tool is for searching by query/tags, but it does not explicitly state when to prefer it over list_context_items or provide exclusion criteria. The use case is inferred but not fully delineated.

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