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

Annotations already declare this is a safe read-only operation, so the description needn't repeat safety. It adds useful semantic context that the output is a comparison of votes cast vs missed per legislator, but does not mention auth needs, pagination behavior beyond the limit param, or response shape.

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?

Three short, front-loaded sentences that each carry information: definition, usage condition, and prerequisite. No filler.

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 analytics endpoint with full schema coverage and annotations, the description is nearly complete. It clarifies the metric being returned, though it could note pagination behavior or typical response ordering.

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 coverage is 100%, so both parameters are already documented. The description adds value by specifying where session_id comes from (list_sessions), but does not explain the limit parameter or add anything beyond the schema baseline.

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?

States a specific metric and scope: per-legislator voted-vs-missed roll-call counts for one session. An agent can distinguish this from generic session tools like get_session_breakdown or get_roll_call by the attendance measure, though no sibling is named explicitly.

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?

Gives a clear use case ('attendance questions') and a concrete prerequisite (session_id from list_sessions). It could go further by saying when to prefer this over get_session_breakdown or get_roll_call, but the context is clear.

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