delete_poll

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

With no annotations provided, the description must disclose behavioral traits. It merely restates the action already implied by the tool name, without explaining whether deletion is permanent, if it cascades to poll questions/answers, or any permission requirements. This is essentially a tautology of the name.

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 sentence with no wasted words. However, it is under-specified, providing only the most obvious statement without any additional useful context. It is concise but not structured in a way that adds value beyond the name.

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 mutation tool with no annotations and no output schema, this description is inadequate. It omits important details such as whether deletion is reversible, how it interacts with published polls, and what effects it has on associated questions and answers. The simplicity of the tool does not excuse the lack of critical behavioral information.

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?

The input schema provides a full description of the sole parameter poll_id ('Poll ID to delete'), so coverage is 100%. The description does not add any additional semantics about the parameter, but the schema already handles it, so baseline 3 is appropriate.

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 'Deletes a poll' uses a specific verb and resource, clearly distinguishing it from sibling tools like delete_poll_question or archive_poll. It directly states the action without ambiguity.

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 is provided about when to use this tool versus alternatives such as archive_poll or delete_poll_question. There is no mention of prerequisites, effects, or exclusions, leaving the usage context entirely to the agent's inference.

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