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

With no annotations, the description must carry behavioral disclosure. It usefully states that the poll's votes and pictures are also deleted and references the DELETE endpoint, but it does not warn about irreversibility, required permissions/auth, or confirmation behavior for a destructive operation.

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 three short sentences and front-loads the action and its cascade. 'Free' is slightly ambiguous and the endpoint reference is optional, but there is no padding or wasted structure.

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?

An output schema exists, so return values need not be explained. However, for a destructive tool with no annotations and only 50% parameter description coverage, the description should say more about irreversibility, auth requirements, and the close_poll alternative; it only covers the deletion cascade.

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 50%: poll_id is documented in the schema as 'the poll's id', while api_key is undocumented in both schema and description. The endpoint path implies poll_id is a path parameter, but the description does not explain the api_key parameter or authentication semantics.

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 states a specific verb and resource: delete a poll, including its votes and pictures. It also maps the operation to DELETE /v1/polls/{poll_id}. It does not explicitly differentiate from close_poll or other poll-related siblings, so this is clear but not fully sibling-aware.

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 usage by saying to delete a poll, but gives no when-to-use guidance, no exclusions, and no comparison to close_poll or other alternatives. For a destructive operation, the absence of any guidance about when deletion is appropriate is a notable gap.

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