u1_multimaterial_readiness

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

With no annotations, the description carries the full burden. It discloses a key behavior: it reports and does not enable, indicating a read-only, non-mutating operation. However, it does not mention return format, permissions, or any other side effects, leaving transparency partial.

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 a single, front-loaded sentence with no filler. Every word serves a purpose, efficiently conveying the tool's action and scope.

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?

The description is too thin for a tool with an undocumented parameter and no output schema. It does not explain what 'model' means or what the readiness report contains, so an agent cannot fully predict invocation or result.

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?

The tool has one optional parameter 'model' with 0% schema description coverage. The description completely omits this parameter, providing no guidance on what to pass or how it affects the report. It fails to compensate for the schema's lack of parameter information.

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 uses a specific verb 'Report' and identifies the resource as 'multi-material support/readiness', clarifying that it does not enable it. This clearly distinguishes the tool from a hypothetical enabling tool and gives a precise purpose.

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 provides a clear context: use it when you need to report multi-material readiness without making changes. The phrase 'without enabling it' implies it is not for enabling, but it does not explicitly name sibling alternatives or conditions for non-use.

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