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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, and an output schema exists, so the safety profile is fully covered elsewhere. The description adds only the "board view" framing and never contradicts the annotations, but contributes no extra behavioral context such as pagination, auth expectations, or result freshness.

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 terse fragments and an invocation example — nothing wasted. The leading "syndicate_board." merely restates the tool name and delays the useful content slightly, keeping it from a 5.

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?

With a rich annotation set, a full schema, and an output schema, the description needn't explain returns or safety. Still, for a tool whose name ('syndicate') maps to propose/debate/vote siblings, the description should clarify that this is the read-only aggregation point; that relationship is only half-drawn.

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 100% for both optional parameters (key, status), so the schema already carries their meaning. The description's fragment "params/proposals/claims" gestures at filtering but adds no syntax, allowed values, or default behavior for `status`.

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?

The description gives a verb ("read") and scope ("params/proposals/claims") plus the framing "board view," so an agent can form a rough picture. But "read params/proposals/claims" is telegraphic and never states what the board actually returns, leaving the core purpose only implied.

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?

It explicitly names a WHEN context and contrasts itself with the court_* sibling family ("claims workflow" vs "board view"), which is real routing guidance rather than a restatement. It stops short of saying when NOT to use it or naming the syndicate_propose/syndicate_vote siblings it complements.

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