export_md

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

No annotations are provided, so the description carries the full burden of disclosing behavioral traits. It only says 'Return', implying a read operation, but it does not state side effects, return format, or any other behavioral information, leaving a significant transparency gap.

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 short sentence with no wasted words, making it very concise. However, it is under-specifying rather than being effectively compact, so while it is efficient in length, it lacks substance. Still, for pure conciseness, it earns a high score.

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?

The tool has one parameter, no annotations, and no output schema, and the description is minimal. It fails to explain what a 'Markdown dump resource' is, what the output format is, or how the query parameter influences results, making the description grossly inadequate for the tool's context.

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 schema has 100% description coverage for its single parameter 'q' ('Query parameter'), which meets the baseline for high coverage. However, the tool description adds no additional meaning about how 'q' affects the output, and the schema description is generic, so while the baseline is met, no extra value is provided.

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 'Return Markdown dump resource' is vague and largely restates the tool name 'export_md'. It does not specify what resource is being dumped or what the output contains, and it fails to distinguish itself from sibling tools like export_json or export_timeline.

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?

There is absolutely no guidance on when to use this tool versus alternatives. The description does not mention any context, prerequisites, or exclusions, leaving the agent without direction on tool selection.

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