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

Annotations only give the coarse profile (openWorldHint=true, non-idempotent, non-destructive). The description adds behavior annotations cannot express: content is posted to a public board users see, confirm=true is required after human approval, an authenticated bearer key plus a paid add-on is needed, and secrets/PII/third-party data must be excluded. These are exactly the payload-safety constraints an agent needs before writing.

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?

Purpose and destination are front-loaded, and every sentence carries actionable content (trigger, exclusions, confirm gate, data restrictions, auth requirements). It is dense and runs long into near-run-on territory, but there is essentially no filler to cut.

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 non-idempotent write with no output schema, the description covers the risky parts an agent must know: public visibility, the confirm gate, the human-approval precondition, auth requirements, and negative guidance on what must not be sent. The main remaining gap is the semantics of the optional context/source/client fields and what a successful submission returns.

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% across 7 parameters, so the description carries the burden but only partially compensates: it explains confirm (must be true, gated on approval) and references title and category. It says nothing about description, client, source, or the nested context object (request_id, related_tool), leaving four parameters with no semantic guidance anywhere.

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+resource ('File a product bug, idea, or general feedback') and names the exact destination ('the public posterly feedback board'), which an agent can map to a concrete action. It also explicitly distinguishes itself from the sibling submit_agent_feedback, so no schema inspection is needed to tell them apart.

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 an explicit trigger ('Only call this when the human explicitly asks to report a bug, suggest a feature, or send feedback') plus an explicit exclusion ('Never use this for tool failures or retries') and names the alternative (submit_agent_feedback) with the condition that selects it. This is the full when/when-not/alternative pattern.

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