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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds real behavioral context beyond that: it discloses authorization scoping ('Technicians see assigned work only') and that blockers are included in the payload. It stops short of return shape or pagination defaults, which keeps it out of the top band.

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?

Two sentences, trigger condition front-loaded, zero filler. The second sentence is a tight capability summary rather than repetition of the title. Slightly more could have been said about filtering semantics within the same budget.

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 an 11-parameter tool with no parameter descriptions and no output schema, the description covers intent and authorization scoping but leaves the agent guessing about defaults (page size, sort order), what a 'blocker' contains in the response, and how unsupplied filters behave. Adequate to invoke, not complete enough to invoke confidently.

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?

With 11 parameters at 0% schema description coverage, the schema provides almost nothing, so the description has to compensate. It does partially: 'search' maps to query, 'filters' implies status/priority/date/assignee/asset/location, and 'pagination' implies page/pageSize. But no individual parameter is explained, and semantics like date-range meaning, defaults, or valid status/priority values are absent.

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 gives a specific verb+resource: it 'loads current authorized jobs with blockers, search, filters and pagination' as an interactive browse view. An agent can tell this is the interactive list view rather than a single-record fetch, though it never names its closest siblings (search_work_orders, view_work_order) to sharpen the distinction.

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?

The opening clause 'Use this when the user wants to browse, search or filter jobs ... interactively' is a genuine use-condition, not just a restatement. But with siblings search_work_orders, view_work_order and view_operations_dashboard in scope, no alternative is named and no exclusion is given — the word 'interactively' is the only routing signal.

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