get_material

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

Without annotations, the description carries full burden. It notes the tool maps to a GET endpoint and is 'readonly-owner', implying no side effects. However, it does not describe error handling, return format, or behavior on missing UUID. The mention of creation requirements is irrelevant and potentially misleading.

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 relatively short but contains extraneous information about creation that does not belong. The sentence about mapping to the API is useful. Could be more streamlined by removing the creation reference.

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 simple get tool with no output schema, the description fails to cover important details like return value structure, potential errors, or any special behavior. It leaves significant context gaps for an AI agent to correctly understand the tool's full behavior.

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%, so the description must explain parameters. It fails to do so: the only parameter 'uuid' is not described, and the phrase 'Required on create: name by UUID' does not clarify its role. No meaning is added beyond the schema.

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 clearly states the tool's purpose: 'Get a single catalog material, product, or labour rate.' It distinguishes from siblings like 'list_materials' by emphasizing 'single'. However, the inclusion of 'Required on create: name by UUID' adds confusion about the tool's function.

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 does not explicitly state when to use this tool versus alternatives. While it implies fetching a single item, there is no direct comparison to siblings like 'list_materials' or 'get_job_material'. No usage exclusions are provided.

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