stape_api

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

No annotations are provided, so the description carries the full burden. It only says 'invoke any endpoint' without disclosing important behaviors like authentication requirements, rate limiting, error handling, or whether it might bypass tool-constructed logic. This is a significant gap for a raw HTTP 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 a single concise sentence. However, it is so minimal that it may be under-specified for a tool of this nature; still, it is efficient and front-loaded. The conciseness earns a 4.

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 is a catch-all for raw API calls with no output schema and multiple sibling tools covering specific use cases, the description lacks important context: it does not mention that users need prior knowledge of the Stape API, that it bypasses built-in tool logic, or any potential risks. It is incomplete for safely using this tool.

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% with each parameter having a description. The description adds no additional meaning beyond the schema. Baseline 3 applies as the schema already documents parameters adequately.

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 it's a 'universal escape-hatch tool to invoke any Stape API endpoint directly,' which distinctly distinguishes it from sibling tools that target specific endpoints. The verb 'invoke' and resource 'Stape API endpoint' are specific and unambiguous.

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 it is for cases not covered by sibling tools via 'escape-hatch', but lacks explicit guidance on when to use it versus alternatives, nor does it state when not to use it. There is no mention of prerequisites or invocation context.

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