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

Annotations only cover non-readonly, non-idempotent, non-destructive; the description adds the substantive constraints: record at most once, only after the user volunteers an opinion, never fabricate or solicit a rating, and that sharing the recording is a separate user choice in the panel. It does not say what happens on a duplicate call or what the call returns, but the key behavioral guardrails are disclosed.

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?

Three short clauses, front-loaded with the core action and followed immediately by the hard constraints. The telegraphic phrasing ('once, only after they give one') is dense but each sentence carries a distinct rule.

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 5-param write tool with no output schema, the description covers the critical agent-facing risks: fabrication, duplication, and timing. Missing only edge behavior such as what a second submission does and whether revision defaults silently.

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 80%, so the baseline is 3; the description goes further by pinning 'rating' to the user's own words ('good or bad as they said it') and 'comment' to a direct quote, which materially constrains how to populate them. 'score_id' and 'revision' remain unexplained beyond the schema.

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: 'Record a user's own opinion of a result.' The phrasing 'a result' is slightly generic, and no sibling (e.g. panel_feedback, review_score) is named as the alternative, so an agent must infer the boundary. Still unambiguous about what is being written.

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 real when-conditions: 'once, only after they give one', plus an explicit prohibition ('Never supply a rating or ask for one'). It does not name which sibling to use instead for panel-side or review workflows, which keeps it below a 5.

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