weflow_sns_block_delete

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

With no annotations, the description carries the full burden of disclosing behavioral traits. It only mentions that actions map to endpoints, but does not explain whether install/uninstall are destructive, whether status is read-only, or any side effects. This is a significant gap for a tool that likely mutates state.

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, front-loaded sentence with no filler words. It is concise and clear, though slightly under-specified. It earns points for efficiency but not full marks due to lack of detail.

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 simple schema (1 param, no output schema) and no annotations, the description is still incomplete. It does not explain the meaning of 'anti-delete', the effects of each action, or any return values. The tool appears straightforward, but the description leaves too much to assume.

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 0%, so the description must compensate. It mentions the action values (status, install, uninstall) that are already in the schema enum, but does not explain what each action does or what the 'endpoints' imply. It adds minimal semantic value beyond 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?

The description clearly states a specific resource ('WeFlow Moments anti-delete status') and a verb ('Manage'), and lists the three actions. It distinguishes from sibling tools by focusing on the anti-delete functionality, though it doesn't fully explain what 'anti-delete' entails.

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 on when to use this tool vs alternatives, nor any context about choosing between status, install, or uninstall. The action enum implies some usage, but the description does not explicitly state any use cases or prerequisites.

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