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 describes the return data (title, author, date, content) and source context (getrecon.substack.com with 36 posts), which adds useful behavioral context. However, it lacks details on error handling (e.g., what happens if the slug is invalid), performance aspects (e.g., latency), or other operational traits, leaving some gaps in transparency.

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 and front-loaded, starting with the core purpose ('Get a full Substack post by slug') followed by return details and source context. Both sentences earn their place by adding value, but the second sentence could be slightly more concise by integrating the source info more tightly, preventing a perfect score of 5.

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 (1 parameter, no output schema, no annotations), the description is mostly complete: it covers purpose, return values, and source context. However, without an output schema, it should ideally describe the return structure more formally (e.g., data types or format), and it lacks error handling details, making it not fully comprehensive for a score of 5.

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 'slug' parameter well-documented in the schema (including examples). The description does not add any additional parameter semantics beyond what the schema provides, such as explaining the slug format or constraints. According to the rules, with high schema coverage (>80%), the baseline is 3 even without extra param info in the description.

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 ('Get a full Substack post by slug') and resource ('Substack post'), distinguishing it from siblings like 'list_substack_posts' (which lists posts) and 'search_substack' (which searches). It explicitly mentions what is returned (title, author, date, content), making the purpose unambiguous and well-differentiated.

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 ('Get a full Substack post by slug'), implying it's for retrieving a specific post rather than listing or searching. However, it does not explicitly state when not to use it or name alternatives (e.g., 'list_substack_posts' for browsing or 'search_substack' for finding posts by query), which would be needed for a score of 5.

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