smart-search

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

With no annotations provided, the description carries full burden. It discloses the critical behavioral trait that the tool returns a StackOverflow search URL rather than actual search results, and explicitly instructs Claude Code to use WebFetch to access that URL. This is valuable context beyond what the input schema provides.

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 extremely concise with only two sentences, both of which earn their place. The first sentence states the purpose, and the second provides critical behavioral information about URL returns and WebFetch usage.

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 search tool with 3 parameters (0% schema coverage) and no output schema, the description provides adequate purpose and behavioral context but leaves parameters completely undocumented. The description covers the essential 'what it does' and 'what it returns' but doesn't address parameter usage.

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 description provides no information about any of the three parameters (query, tags, sort), and schema description coverage is 0%. The description doesn't compensate for this gap by explaining what these parameters mean or how they affect the search.

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 StackOverflow for technical problems and solutions, which is a specific verb+resource combination. However, it doesn't explicitly differentiate from sibling tools like ai_search_github or ai_search_web beyond mentioning StackOverflow specifically.

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 usage context by specifying 'technical problems and solutions' and mentions that Claude Code should use WebFetch to access the returned URL. However, it doesn't provide explicit guidance on when to choose this tool versus other search siblings like ai_search_github or ai_search_docs.

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