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

Discloses 'soft delete' and 'stops future deliveries' but does not mention required permissions, reversibility, error cases, or response format. With no annotations, more detail would improve 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?

Single sentence, front-loaded with action and resource, no extraneous words. All information is relevant and efficiently presented.

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 simplicity (1 required param, no output schema), the description covers key aspects (action, effect, parameter role). Could mention typical response or error conditions but is largely sufficient.

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 0%; description only adds 'by id' to indicate the parameter purpose. Does not specify format, constraints, or how to obtain the ID. Minimal added value over the schema.

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?

Clearly states the action ('Deactivate'), the resource ('freshness webhook subscription'), and the mode ('soft delete; stops future deliveries'). Distinguishes from siblings like freshness_subscribe (create) and freshness_list (list).

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?

Implies use when you have a subscription ID and want to stop deliveries. Lacks explicit when-not or alternatives, but the sibling tools are distinct enough that the context is clear.

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