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

Annotations already declare destructiveHint=true, idempotentHint=true and readOnlyHint=false, so reversibility and mutation risk are covered structurally. The description adds the authorization constraint (ownership) that annotations cannot express, though it does not restate whether deletion is permanent or what an idempotent repeat returns.

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?

Two sentences, front-loaded with the action and its scope, then the exclusion. No filler and nothing redundant with the annotations.

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 two-parameter tool with no output schema, the ownership rule and exclusion are well covered, but the description leaves target_id semantics and post-delete behavior (permanent vs. recoverable, error on non-owned ID) unstated.

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 carry parameter meaning. It only repeats the target_type enum values already in the schema and says nothing about target_id — its expected format, where to obtain an ID, or whether it is a post/reply slug or numeric ID.

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?

States a specific verb (delete), a specific resource (your own Forum posts or replies), and narrows scope with an enumerated target_type. The ownership restriction plus the pointer that others' content is out of scope distinguishes it cleanly from agora_report and agora_post.

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?

Gives the positive condition (your own post/reply), the exclusion (others' content), and the alternative path (report it), which maps to the sibling agora_report. An agent can pick between delete and report without opening either schema.

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