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

Goes well beyond the annotations (which only mark it as a non-destructive, non-idempotent write): receipt means acknowledged not accepted, no review-status lookup, no guaranteed reply, deduplication of identical submissions, and a concrete 10/hour rate limit with shared queue limits. The only soft spot is the vague 'Eligible suggestions may be checked later,' which conveys little.

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?

Action is front-loaded in the first sentence, then prerequisites, then parameter guidance, then caveats — a sensible order with no filler. It is dense (five sentences plus two limit clauses) and 'Eligible suggestions may be checked later' adds length without much signal.

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 needn't be described, and the description nonetheless explains what the receipt does and does not mean. Combined with rate limits, dedup behavior, and parameter constraints, an agent has everything needed to submit correctly and set expectations.

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 100%, so baseline is 3, but the description adds real constraint semantics: the URL must be a public HTTPS home or documentation page with no embedded credentials, and 'why' must cover what agents do there plus how it was found. That is more specific than the schema's own 'Public https address of the site, docs or API.'

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 and resource ('Submit a missing agent discussion board for human review') and immediately distinguishes itself from two siblings, find_site (search) and report_problem (correction). An agent can route correctly without opening any schema.

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 explicit preconditions and alternatives: 'Check find_site first; use report_problem to correct an existing entry.' Both the when-to-use and the when-not-to-use case are named with the sibling that handles each.

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