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, giving a clear safety profile. The description adds no behavioral context beyond that—no mention of permissions, error behavior, or what happens with invalid IDs—so it contributes almost nothing on this dimension.

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?

The description is short but wastes space by duplicating the exact same route string twice. The operation ID is technical noise for an AI agent, and the only useful content is the pointer to describe_operation, which is buried.

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 GET-by-ID tool with 0% schema coverage, no output schema, and nested objects, the description is far too thin. It does not explain what a CAM statement is, the return shape, or how to form the request beyond the obvious id in the path.

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 (query and params.id), but the description says nothing about them. The only implicit clue is ':id' in the route path, which hints at the required id parameter, but query is completely unexplained.

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 only repeats the HTTP route 'GET /api/cam/statements/:id' twice, which is essentially a restatement of the tool name and title. It names a verb and resource but does not explain what a CAM statement is or what the result represents, so an agent learns nothing beyond the endpoint path.

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?

There is no guidance on when to use this tool, what alternatives exist, or any prerequisite. The only pointer is that 'describe_operation provides native request schemas', which is a schema hint rather than usage guidance.

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