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

Annotations already declare readOnlyHint=true, so safety is covered; the description adds useful context beyond that by disclosing the raw GET endpoint and the response envelope shape ({ meta, response }). It does not discuss pagination limits behavior or rate limits, but for a read-only list tool this is solid added context.

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 with no filler: identity disambiguation first, then API mapping, then pagination support and return shape. Every clause carries information an agent can use.

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?

There is no output schema, and the description mitigates that by naming the { meta, response } envelope. With zero required parameters and full schema coverage, nothing essential is missing, though it could say a bit more about what each returned job object contains.

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% and each of the five parameters already has detailed documentation, including filter syntax and ordering examples. The description only enumerates the same parameter names (_page/_limit/_fields/_filters/_search) without adding syntax or semantics, so the baseline 3 applies.

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 verb (List) and resource (jobs), and immediately resolves the terminology trap by clarifying that Accelo "jobs" are projects. It even names the underlying endpoint (GET /api/v0/jobs), so an agent can distinguish it from get_job and the parallel list_* siblings without opening any schema.

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?

Usage is implied by the list-vs-get naming convention shared with siblings, but there is no explicit statement of when to prefer this over get_job, accelo_request, or a filtered list. No exclusions or prerequisites are given.

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