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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and closed-world, so the safety profile needs no repetition. The description adds nothing beyond those hints — no note on what a badge represents, whether it is computed on the fly, or its cost/side effects.

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 endpoint string is duplicated verbatim in back-to-back sentences, so space is wasted rather than earned. The operation ID and describe_operation pointer are metadata, not substance.

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?

No output schema exists, so the description should explain what the caps badge payload contains; it does not. For a nested-object request with an undocumented query parameter, the definition leaves the agent without enough to invoke it confidently.

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% with two parameters (query object and params.periodId), and the description provides no meaning for either. An agent must infer what the free-form query object accepts and what a periodId identifies.

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 restates the HTTP route (GET /api/cam/periods/:periodId/caps-badge) already present in the title, so it is effectively a tautology. It implies a resource (a caps badge for a CAM period) but never says what is returned or how it differs from sibling endpoints like get_cam_periods_by_periodId_caps_summar.

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 about when to use this endpoint versus the many sibling CAM period endpoints (caps_summary, approval, recalcs, statements). The only pointer is to describe_operation for schemas, which is not usage guidance.

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