Look up issuing materials

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

Annotations already declare readOnlyHint, openWorldHint, and idempotentHint, covering the safety profile. The description adds that the tool supports 'standard JobBOSS2 filters and paging', but nothing beyond that; no side effects, auth requirements, or edge-case behavior are disclosed.

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 description is one concise sentence with no filler. It front-loads the core purpose and keeps the supporting details about filters and paging compact.

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 read-only lookup tool with annotations and an output schema, the description covers the basic purpose. Still, the lack of parameter semantics and explicit usage guidance means an agent would likely need to inspect the schema closely before constructing a valid invocation.

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 0%, and the description only gestures at 'standard JobBOSS2 filters and paging' without explaining skip, take, sort, fields, or filters. It does map the lookup enum to human-readable categories (bin locations, job numbers, routing steps), but this is insufficient for a 6-parameter tool with no schema-level descriptions.

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 names a specific verb ('List') and concrete resources: 'issuing-material bin locations, job numbers, or routing steps'. It clearly distinguishes this lookup tool from generic siblings like jobboss2_list and jobboss2_get.

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 description implies when to use it: when the agent needs issuing-material reference data such as bin locations, job numbers, or routing steps. However, it does not explicitly state when not to use it, nor does it name alternatives like jobboss2_get or jobboss2_transfer_stock_to_job.

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