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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered without the description. The description adds nothing beyond structured data — no note on returns, pagination, the enclosing 'query' object, or what 'recalc' rows contain. No contradiction with annotations, but no added value either.

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?

Extremely short but not concise in the useful sense: the same endpoint string is duplicated verbatim, and the second sentence is metadata (operation ID) that does not help selection. There is no front-loaded statement of purpose.

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 nested-object tool (params + free-form query) with no output schema and 0% parameter description coverage, the description leaves the agent without enough information to call it confidently — neither the meaning of the period scope nor the shape of accepted query filters is conveyed.

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 the description supplies no parameter meaning. The path template ':periodId' weakly maps to the required 'params.periodId', but the untyped free-form 'query' object is left entirely unexplained in both schema and description.

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 literal path repeated twice: 'GET /api/cam/periods/:periodId/recalcs. GET /api/cam/periods/:periodId/recalcs.' This restates the name/title rather than explaining in words what a recalculation record is or what the response represents. It does signal a read of a period-scoped sub-resource, but no natural-language verb+resource statement distinguishes it from siblings like get_cam_recalcs_by_id or the other get_cam_periods_by_periodId_* tools.

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 when-to-use guidance and no mention of alternatives, despite many close siblings (get_cam_recalcs_by_id, get_cam_periods_by_periodId_*, get_cam_periods). The only directional hint is 'describe_operation provides native request schemas', which points to a helper tool rather than explaining when this operation applies.

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