Delete Footer Comment

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

The description only repeats the action 'Delete' without adding any behavioral context beyond the annotations. It does not disclose whether deletion is permanent, whether it is reversible, or any permission requirements. The annotations (destructiveHint=true, idempotentHint=true) carry the entire burden, but the description adds no additional insight.

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 extremely short but under-specified rather than appropriately concise. It contains only the tool name and a restatement of the parameter, providing no useful instructions or context.

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 destructive operation with no output schema, the description inadequate. It fails to explain the effect of the deletion, any consequences, or how it fits into the broader API workflow. The minimal description does not give an agent enough context to invoke the tool confidently.

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%, so the description must compensate. It merely restates 'comment_id: Comment ID', which duplicates the schema property title and provides no additional meaning, such as the required format, existence requirements, or relationship to other resources.

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 the verb 'Delete' and the resource 'footer comment', which is specific and distinguishes it from sibling tools like delete_page or delete_inline_comment. However, it does not explicitly differentiate from similar deletion tools, relying on the name itself for that distinction.

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 versus alternatives. The description does not mention prerequisites, exclusions, or relationships to sibling operations like list_footer_comments or get_footer_comment.

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