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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is clear. The description adds modest behavioral context by specifying which fields the query searches, but it does not disclose matching behavior, pagination, or result formatting. With annotations covering the core behavior, a 3 is appropriate.

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 sentence that front-loads the verb and resource and efficiently enumerates the searchable fields. There is no redundant or vague wording; every phrase contributes to understanding the tool's purpose.

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 one-parameter, read-only, non-destructive search tool with full schema coverage and safety annotations, the description provides the key contextual detail of which fields are searched. It does not specify query syntax or return shape, but those are not essential for an agent to invoke this simple tool correctly. A small gap remains around expected output, but overall it is sufficiently complete.

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?

The schema describes the single parameter 'q' only as 'Search query', which is minimal. The tool description compensates by explaining that q matches against title, client, category, role, stack, or description, adding meaningful semantics beyond the schema. Given the high schema coverage baseline is 3, this added context pushes it to 4.

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 ('search') on a specific resource ('case studies') and enumerates the fields searched. However, it does not explicitly differentiate this from sibling tools like fetch_project_case_study or list_portfolio_projects beyond the generic 'search' verb, so it misses the full 5-point criterion of distinguishing from siblings.

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 no guidance on when to use this tool versus its siblings. It does not mention that this tool is for free-text search across fields while fetch_project_case_study likely retrieves a single case study or list_portfolio_projects enumerates all projects. There is no exclusions or alternative routing.

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