get_job_material

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

No annotations provided; description adds 'tier: readonly-owner' indicating read-only access, but lacks details on side effects, authentication, or response behavior. Incomplete disclosure for an unannotated tool.

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 concise sentences; first is clear, second is cryptic, third is technical. No unnecessary words, but could be restructured for clarity.

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?

Covers basic purpose and endpoint mapping for a simple single-param tool, but omits output details and typical use context. Adequate but not comprehensive.

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 0%; description adds 'Required on create: quantity by UUID' which suggests uuid identifies a line item, but does not clarify format or purpose beyond the schema's type 'string'.

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?

Clearly states 'Get a single line item (material/labour/service) on a job's quote or invoice.' This provides a specific verb and resource, distinguishing it from list_job_materials and other retrieval tools.

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?

Implies use when you have a specific UUID, but does not explicitly compare to alternatives like list_job_materials. The phrase 'Required on create: quantity by UUID' is ambiguous and does not clearly state when to use this tool.

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