get_conversion

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

No annotations are available, so the description carries the full burden. It discloses the read-only nature ('Retrieve') and the return format ('full Markdown content'), but does not mention error behavior, edge cases, or side effects. This is minimally acceptable but lacks depth for a tool without annotation support.

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, concise sentence that front-loads the purpose and includes essential details (full Markdown content, by ID). Every word earns its place, and there is no wasted text.

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 retrieval tool with one required parameter and no output schema, the description adequately conveys the return type and purpose. It does not cover error handling or prerequisites, but given the low complexity and schema coverage, the description is complete enough for selection and invocation.

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 input schema fully describes the only parameter ('id' as 'The conversion ID'), and the description's 'by its ID' is a restatement rather than additional semantic value. With 100% schema coverage, the baseline of 3 applies since the description adds nothing 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 uses a specific verb ('Retrieve') and identifies the resource ('full Markdown content of a previously saved conversion') and the key qualifier ('by its ID'). This clearly distinguishes it from sibling tools that perform conversions or searches rather than retrieving existing conversions.

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 implies usage context ('previously saved conversion') but does not explicitly state when to use this tool versus alternatives or when not to use it. The sibling list shows other tools, but no direct comparisons or exclusions are provided, so guidance is only implicit.

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