recon-fuzz-knowledge

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

With no annotations provided, the description carries full burden for behavioral disclosure. It states what the tool does but doesn't describe how it behaves: no information about response format, error handling, authentication needs, rate limits, or whether it's a read-only operation. For a tool with zero annotation coverage, this leaves significant gaps in understanding its operational characteristics.

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 appropriately sized with two sentences: the first states the core purpose, and the second enumerates covered concepts. It's front-loaded with the main function and avoids unnecessary elaboration. The concept list could be slightly overwhelming but serves a clear informational 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?

Given the tool's moderate complexity (single parameter, no output schema, no annotations), the description is adequate but incomplete. It explains what concepts are available but doesn't cover behavioral aspects or output format. For a concept lookup tool, users need to know what kind of explanation to expect, which is missing here.

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 description coverage is 100%, so the schema already documents the single 'slug' parameter with examples. The description adds value by listing specific concept topics that correspond to valid slugs, providing semantic context beyond the schema's technical definition. This justifies a baseline score of 3 since the schema does the heavy lifting but the description enhances understanding.

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 verb 'Get' and resource 'technical concept explanation from the Recon Book', making the purpose specific and actionable. It distinguishes from siblings by focusing on concepts rather than chapters, posts, or search operations, and provides a comprehensive list of covered concepts to clarify scope.

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 concept explanation from the Recon Book' and listing covered topics, which helps differentiate it from siblings like get_blog_post or get_book_chapter. However, it doesn't explicitly state when not to use this tool or name specific alternatives for overlapping functions.

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