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

Annotations already declare the mutation profile (readOnly=false, destructive=false, idempotent=true), so the bar is lower, yet the description adds real behavioral context: a withdraw token returned exactly once, a rigor breakdown that scores form not truth, and the 'acceptance is not endorsement' caveat. It stops short of describing failure/rejection behavior or rate limits.

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-loads the action in the first clause and keeps the rest to prerequisites, returns, and next step. It is dense but every sentence carries information; only the parenthetical tool references add mild clutter.

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 10-parameter mutation tool with no output schema, the description helpfully explains the return (withdraw token, rigor breakdown) and the prerequisite/follow-up chain. What is missing is failure handling and any hint about the optional parameters' effect, but the core call path is fully covered.

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% with per-field descriptions, so the schema already carries the parameter burden. The description restates the required inputs (falsifiable claim, method, falsification condition, answering id) but adds no syntax, format, or constraint detail beyond what the schema provides.

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 ('PUBLISH A RESULT') and immediately scopes it to the two artifacts it can attach to, naming the sibling tools (get_open_questions, get_research_curriculum) that supply those ids. An agent can distinguish this from list_findings, get_finding, or review_finding 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 clear usage context: use it to publish a result against an open question or a curriculum objective, and points to the source tools for the id plus the follow-up (list_findings). It does not state exclusions (e.g., what to do with a result that is not falsifiable), but the routing is explicit enough to select correctly.

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