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 of behavioral disclosure. It adds some context: it specifies the return format ('top 5 matching glossary terms with full definitions') and the data source ('getrecon.xyz'), which are useful beyond basic functionality. However, it lacks details on error handling, rate limits, or authentication needs, leaving gaps for a tool with no annotation support.

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 highly concise and well-structured in two sentences. The first sentence clearly states the tool's purpose, and the second adds valuable context about returns and source. Every sentence earns its place without redundancy, making it easy for an agent to parse quickly.

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 low complexity (one parameter, no annotations, no output schema), the description is moderately complete. It covers the basic action and return format but lacks output schema details (e.g., structure of returned terms) and deeper behavioral context. For a simple search tool, this is adequate but leaves room for improvement in guiding agent 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 input schema has 100% description coverage, with the single parameter 'query' documented as 'The search query to find glossary terms.' The description does not add any additional meaning beyond this, such as query syntax examples or search behavior nuances. With high schema coverage, the baseline score of 3 is appropriate, as the schema adequately handles parameter documentation.

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: 'Search the Recon glossary for terms matching a query.' It specifies the verb ('search'), resource ('Recon glossary'), and scope ('terms matching a query'), making the intent unambiguous. However, it does not explicitly differentiate this glossary search from sibling tools like 'search_all' or 'search_book', which could help an agent choose between similar search functions.

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. It mentions the source ('getrecon.xyz'), but does not indicate scenarios where this glossary search is preferred over other search tools (e.g., 'search_all' or 'search_book') or when it might be inappropriate. Without such context, an agent must infer usage based on tool names alone.

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