uxpass_report_md

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

No annotations exist, and the description adds no behavioral traits (e.g., read-only, authentication needs, side effects). It only restates the purpose without any operational constraints.

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 with no redundancy. However, it could be slightly more informative without sacrificing brevity.

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?

Given the tool's simplicity and presence of siblings, the description lacks context about the report's origin (e.g., requiring a prior uxpass_run) and format details. It is incomplete for an agent to confidently invoke the tool.

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?

Although schema coverage is 100% for run_id, the description adds no meaning beyond the schema. It does not explain how to obtain a run_id or any validation constraints, leaving the agent with only the schema's basic description.

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 clearly states the verb 'Get' and resource 'Markdown report for a UXPass run', distinguishing it from sibling tools like uxpass_report_html and uxpass_report_json which return different formats.

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?

No guidance is provided on when to use this tool versus alternatives like uxpass_report_html or uxpass_report_json. The description lacks context for selecting the correct report format.

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