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

With no annotations provided, the description carries the full behavioral burden. It explicitly states the tool is read-only, requires no authentication, returns a structured JSON report with severity/issues/summary/stats, and lists the exact checks performed. This gives an agent a solid mental model of behavior and side effects.

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 compact and information-dense: purpose, return format, check categories, and usage context are all covered in four sentences. Every sentence contributes value, and the core purpose is front-loaded.

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?

Although there is no output schema, the description explains the return structure. It also covers the input domain, the check scope, the read-only/no-auth behavior, and the intended usage scenario. An agent has enough context to select and invoke the tool correctly.

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 100%, so the schema already documents both parameters fully. The description adds no parameter-specific meaning beyond what the schema provides, which matches the baseline of 3 for high schema coverage.

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 and resource: static compatibility checking of URDF XML files. It enumerates ten concrete check categories, making the tool's scope unmistakable and clearly distinguishing it from the sibling tools, which target BOM/component compatibility rather than URDF files.

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 gives a clear use case: pre-upload compatibility validation for URDF files in RoboParts. It does not explicitly state when not to use this tool or name alternatives, but the resource-specific context is enough to guide an agent away from the component/BOM-focused siblings.

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