export_skill_md

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

With no annotations, the description carries the behavioral burden. It says the operation is a read that returns markdown and discloses the optional side effect: writing to a path when provided. It does not detail overwrite/permission behavior, but the core behavior is transparent.

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 tight sentences with no filler. The core transformation is front-loaded, and the optional write behavior is appended without redundancy.

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 two-parameter tool with an output schema, the description is largely complete: it defines the artifact, the return value, and the optional side effect. Minor details like path overwrite semantics are absent, but the essential calling context is present.

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 0%, but the description maps item_id to 'one of the seller's skill listings' and explains path's effect: 'when `path` is given, also writes it there.' This adds meaning beyond the bare schema titles and compensates for the lack of schema descriptions.

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 opens with a specific verb ('Read') and resource ('one of the seller's skill listings') and clarifies the output format ('the SKILL.md it compiles to — the same file a buyer downloads'). This also distinguishes it from get_listing by focusing on the compiled markdown artifact rather than listing metadata.

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 makes the use case clear: retrieve the compiled SKILL.md file that corresponds to a skill listing, not the listing's metadata or source draft. It does not explicitly name alternatives or exclusions, but the context strongly implies when this tool is appropriate.

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