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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and closed-world, so the safety profile is covered. The description adds genuinely new context that annotations cannot express: a 5 calls/hour per-IP free tier, an 8 KB argument cap, and $0.005 USDC per call via x402 once exceeded — exactly the auth/rate-limit disclosure the dimension rewards. It also signals the output shape ('errors and warnings with fixes') but omits whether warnings block validation.

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?

Two sentences, zero waste: the capability and its provider targets come first, then the pricing/quota constraint. Nothing is repeated from the schema or title.

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 validation tool with 100% schema coverage and no output schema, the definition covers purpose, providers checked, result shape, and cost/limits. The main remaining gap is what a 'supported format' for the `tool` object is and whether warnings are blocking.

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 100%, so both `tool` and `targets` are documented in the schema, including the enum values and the 'Default: all' behavior. The description adds only the 8 KB argument size cap, which is a useful constraint but tangential to parameter meaning; baseline 3 applies when the schema carries the load.

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?

States a specific verb (check/lint) and resource (LLM tool definition) and enumerates the provider rule sets it validates against, which is much more than the title restates. It implicitly separates itself from batch_convert_tool_schemas by scoping to 'one' definition, but it never names a sibling or explicitly distinguishes linting from the convert_* family.

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 use case (validate a definition before shipping it against provider rules) is implied by the description, and the free tier explains when the tool is practical. There is no explicit 'use this instead of convert_tool_schema' routing and no stated preconditions for what a valid input looks like.

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