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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so safety is fully covered without the description. The description adds nothing beyond that: no mention of pagination via cursor/limit, no note that results default to active-only status, and no indication of what the returned fields are.

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?

It is a single short fragment with no waste, but it is under-specified rather than concise: it reads as a field listing without a leading verb or the tool's actual behaviour front-loaded.

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 5-parameter, filterable list tool with no output schema, the description should at minimum state that it lists jobs, note pagination and the default active-status filter, and route to get_job for a single record. It does none of these, though annotations and schema cover safety and most parameters.

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 effectively 80% (all parameters except 'limit' carry descriptions, including the important 'active (default)' status semantics). The description mentions output fields that do not map to any parameter, so the schema is doing all the work; 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?

The description is a noun fragment ('Jobs with number, customer, site address, status and assigned staff') that restates the resource and its fields but supplies no verb and no scope. Only the name/title ('list_jobs') tell the agent this is a listing operation, and nothing distinguishes it from get_job or list_customers.

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 tool versus get_job (single record) or the other list_* siblings. Prerequisites, pagination workflow, and default filtering behaviour are left entirely to inference from the schema.

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