DeleteStore

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

No annotations exist. Description only states 'delete', but does not disclose consequences (e.g., irreversibility, cascading effects, required permissions). Lacks behavioral context beyond the action itself.

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?

Single sentence, no fluff. Every word is necessary and front-loaded. Highly efficient.

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 simple tool with no parameters or output schema, the description is minimally adequate. However, it lacks details on prerequisites, side effects, or how the store is identified, which could confuse an agent in a large ecosystem of related tools.

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?

No parameters required; schema coverage is 100% with an empty object. Description implicitly confirms no additional input needed, but does not explicitly state that the tool operates on a store identified by context. Baseline 3 adjusted up for zero 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?

Description 'Delete a store' clearly states action (delete) and resource (store), distinguishing from sibling tools like CreateStore, UpdateStore, GetStore. It is 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?

No guidance on when to use DeleteStore versus alternatives (e.g., TerminateCurrentContract, DeactivateSubscription). No prerequisites or conditions provided.

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