recon-fuzz-knowledge

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

No annotations are provided, so the description carries the full burden. It discloses key behavioral traits: it searches 'across all Recon Substack posts', returns 'top 10 matches', and specifies the output format ('titles, dates, and content snippets'). However, it doesn't mention search algorithm, ranking criteria, pagination, error conditions, or authentication needs.

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 (two sentences) and front-loaded with the core functionality. Every word earns its place: the first sentence defines scope and action, the second specifies output format and limit. No wasted words 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?

Given the tool's moderate complexity (search operation with ranking and formatting), no annotations, and no output schema, the description provides basic but incomplete context. It covers what the tool does and what it returns, but lacks details about search behavior, error handling, and differentiation from similar tools, which would be helpful for an agent.

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 input schema has 100% description coverage, with the single parameter 'query' documented as 'The search query'. The description doesn't add any parameter-specific information beyond what the schema provides, maintaining the baseline score of 3 for high schema coverage.

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's purpose: searching across Recon Substack posts and returning top 10 matches with specific fields (titles, dates, content snippets). It uses specific verbs ('Search', 'Returns') and identifies the resource ('Recon Substack posts'), but doesn't explicitly differentiate from sibling tools like 'search_all', 'search_book', or 'get_substack_post'.

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 provides no guidance on when to use this tool versus alternatives. With multiple search-related siblings (search_all, search_book, search_site) and content retrieval tools (get_substack_post, list_substack_posts), there's no indication of scope boundaries, use cases, or prerequisites.

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