recon-fuzz-knowledge

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It effectively describes key traits: the action is a forced refresh (implying mutation), it affects all three sources, and it includes a critical rate limit ('once per 60 seconds'). However, it doesn't cover aspects like error handling or response format.

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, efficient sentence that front-loads the core action ('force refresh the documentation cache') and includes essential details (sources and rate limit) without any wasted words. Every part earns its place.

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 (a mutation with rate limits), no annotations, and no output schema, the description is mostly complete. It covers the purpose, scope, and a key behavioral constraint (rate limit), but lacks details on what 'refresh' entails operationally or what the response looks like.

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 0 parameters with 100% coverage, so the baseline is 4. The description adds no parameter-specific information, which is appropriate given no parameters exist, maintaining the baseline score.

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 specific action ('force refresh') and the target resource ('documentation cache'), explicitly listing all three sources (getrecon.xyz, book.getrecon.xyz, getrecon.substack.com). It distinguishes this tool from siblings like 'get_blog_post' or 'search_all' by focusing on cache management rather than content retrieval.

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 clear context for when to use this tool ('force refresh the documentation cache'), but does not explicitly state when not to use it or name alternatives. It implies usage when cached documentation needs updating, though lacks exclusions like avoiding use during high traffic.

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