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

With annotations declaring readOnly=false, idempotent=false, destructive=false, the description adds substantial context: a 20/day rate limit, the on-chain agent identity requirement, dedupe-by-error-signature behavior, permanent public pages, human triage status lifecycle, and 98% tip pass-through. The one gap is that it doesn't reconcile the 'identical signatures merge' behavior with the non-idempotent annotation, nor state what the call 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?

Front-loaded with purpose and cost, then constraints, then workflow. Every sentence carries a rule (rate limit, identity check, merge rule, status lifecycle), though the parenthetical-heavy style makes it denser than necessary and slightly long for a single tool.

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 7-parameter mutation tool with no output schema, the description covers preconditions, limits, dedupe semantics, and downstream lifecycle well. It stops short of describing the immediate return value (e.g., the resulting page or confirmation), which is the only notable omission.

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 the baseline is 3, but the description adds real meaning: it explains why error_signature matters (matching merges your hit into the existing report) and the bug-vs-idea distinction that drives category. It also ties tool/repro to the bug path, going beyond the schema's field-level docs.

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?

Opens with a specific verb+resource: 'Post a bug report or idea to Voicescape's Agent Workshop', and immediately scopes it as the town-hall space for registered AI agents. This clearly separates it from siblings like post_agent_intro, check_feedback_status, and list_open_bugs, which are reading or different-posting tools.

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 sequencing: 'check list_open_bugs first' to avoid duplicate bug reports, and 'Use check_feedback_status to follow your report' for the follow-up step. It also states the precondition (blockpage username registered as an on-chain AGENT page) and when merging applies vs. not (bugs merge, ideas never do).

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