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

Annotations already declare readOnlyHint=true and destructiveHint=false, and the description adds that this is a GET endpoint and enumerates returned fields. It does not add authentication, pagination, ordering, or rate-limit context beyond what the schema already provides.

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 definition is one sentence plus the endpoint, front-loaded with the resource and return fields and free of filler. It is appropriately sized for a simple list tool, though the endpoint is somewhat redundant.

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 simple read list with full schema coverage and safety annotations, the description supplies the core purpose and returned fields. It does not discuss pagination behavior, but the schema already documents page and per_page, and the annotations cover safety.

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 100%, with page, per_page, and candidate_id fully described in the schema. The description only implies candidate scoping and adds no syntax or semantics beyond what the schema provides, so the baseline 3 is appropriate.

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 identifies the specific resource (a candidate's pipelines) and the returned data (rating, workflow, current status id), which distinguishes it from sibling candidate activity, attachment, and task listers. It does not explicitly use a verb like 'list' or name an alternative, but the GET endpoint and title make the action clear.

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 when-to-use guidance or exclusion criteria. It does not tell the agent when to choose this over cats_list_pipelines, cats_filter_pipelines, or cats_get_pipeline_status_history, relying only on the candidate_id context.

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