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

Beyond the annotations (readOnly, idempotent, non-destructive, openWorld), the description discloses real operational traits: rate limiting (10 calls/day free), the paid fallback path and auth mechanism (X-API-Key credits), plus error behaviour (line-numbered errors) and multi-document handling. It doesn't describe response structure, but an output schema exists to cover that.

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 with the core purpose front-loaded and no wasted wording. The rate-limit sentence is compact and each clause adds actionable information for an agent deciding whether to call.

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 two-parameter, read-only conversion tool with a complete schema, rich annotations, and an output schema, the description covers purpose, capability edge cases, and cost/auth constraints. Only the usage comparison to sibling conversion tools is left unstated.

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 both 'input' and 'direction' are already documented, including the auto-detection hint. The description adds only indirect context (that multi-document YAML input is supported) and no additional syntax or format constraints, so the baseline 3 applies.

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 resource and both directions explicitly: 'YAML ... to JSON, or JSON to YAML', with a distinguishing detail (multi-document support, line-numbered errors). An agent can immediately separate this from siblings like json_format or csv_json_convert by the format pair.

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?

Usage is implied by the bimodal phrasing and the 'direction' parameter description ('auto'), but there is no explicit when-to-use or when-not-to-use guidance against neighbouring tools such as json_format. The agent must infer that this is the tool for cross-format conversion rather than validation or formatting.

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