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

readOnlyHint=true already tells the agent this is a safe read, so the bar is lower. The description earns credit beyond that by disclosing the underlying endpoint (GET /api/v0/jobs) and the response envelope { meta, response }, which the annotations do not convey.

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 sentences, zero filler, and the most disambiguating fact (jobs = projects) is front-loaded. Every clause carries information the agent needs.

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?

With no output schema, the description usefully states the return envelope, and the schema fully covers inputs. What is missing is lighter than what is present: no note on empty-result behavior or whether the list is workspace-scoped.

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%, so the schema already documents all five parameters including pagination defaults and Accelo filter syntax. The description only restates the parameter names (_page/_limit/_fields/_filters/_search), adding no semantics beyond the schema — the baseline of 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 and resource ("List jobs") and immediately disambiguates the domain term: "Accelo 'jobs' are projects." An agent can confidently distinguish this from get_job or list_tasks without opening a 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 only implied by the name and the enumerated query features; there is no explicit when-to-use, no prerequisite, and no routing to siblings such as get_job (single record) or accelo_request (raw API). The listing of supported parameters nudges toward 'use this to enumerate jobs', but no alternatives or exclusions are named.

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