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. The description adds nothing beyond that - no indication of what data is returned, side effects, auth scope, or pagination.

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 text is short but wastes its single sentence on duplicating the same path string twice, then appends a boilerplate operation ID and schema pointer. No front-loaded purpose statement exists to earn the space.

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 with 0% schema coverage, no output schema, and dense sibling overlap in the CAM namespace, the description provides essentially nothing an agent needs to call it correctly or know what it returns.

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% for two parameters, including a required nested object with periodId. The description's only contribution is echoing the ':periodId' path placeholder, which at least maps the required param to a CAM period identifier, but it never explains period semantics or what the free-form 'query' object accepts.

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 path and title verbatim ('GET /api/cam/periods/:periodId/caps-summary' twice) with no explanation of what a CAM caps summary actually contains. An agent cannot distinguish it from siblings like get_cam_periods_by_periodId_caps_badge or get_cam_periods_by_periodId without reading the tool names.

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 endpoint versus the many other cam/periods sub-resource tools. The only actionable hint is 'describe_operation provides native request schemas', which is a schema-lookup pointer, not usage guidance.

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