API request

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

With no annotations, the description adds useful context that the call is authenticated, generally POST-only, and intended for destructive operations. However, it does not describe permissions, reversibility, side effects, or error behavior for a generic destructive-capable API tool.

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 short and front-loads the key guidance about preferring dedicated tools and using this for rare or destructive endpoints. The phrasing is slightly telegraphic, but there is little wasted text.

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?

For a generic API escape hatch with no output schema and no annotations, the description covers usage well but leaves gaps around return format, error handling, and safety expectations for destructive calls. The schema handles parameter structure, but the behavioral context is only partially complete.

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 coverage is 75%, so the schema already documents most parameters. The description reinforces the POST-only nature and gives endpoint examples, but it does not add much detail about how to use the body or query parameters.

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 that this is a generic authenticated Simple API call and distinguishes it from dedicated tools. It also names destructive endpoint examples, though the resource remains broad and generic by design.

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?

It explicitly says to prefer dedicated tools when available and to use this for destructive operations and rare endpoints. It also clarifies the mostly POST-only behavior of the Simple API, giving clear selection guidance.

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