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, so the safety profile is covered. The description adds nothing beyond that: no pagination, no ordering, no empty-result behavior, no auth scoping note, and the duplicated path sentence carries zero behavioral content.

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?

Two sentences, but the first is the identical path string printed twice — pure redundancy that pushes the one useful sentence (the describe_operation pointer) to the end rather than front-loading it.

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 read-only sub-resource GET with a nested untyped query object, 0% schema description coverage and no output schema, the description should at minimum say what anchors are returned and how to filter them. It supplies neither, leaving the agent dependent on describe_operation for anything actionable.

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% and there are two parameters, one of which is a free-form nested 'query' object with additionalProperties. The ':clauseId' path token implies the required clause identifier, but the description never says what clauseId format to supply, what query keys are accepted, or what filtering the anchors endpoint supports.

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 is the URL path repeated verbatim twice, which only restates the tool name/title (cam: GET /api/cam/clauses/:clauseId/anchors). It never explains what an 'anchor' is on a CAM clause or how this differs from siblings such as get_document_anchors or get_cam_clauses_by_id_categories.

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?

No statement of when to use this over alternatives, no prerequisites, no exclusions. The only procedural hint is 'describe_operation provides native request schemas', which points at a sibling for schema lookup but gives no condition that selects this tool.

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