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

The readOnlyHint annotation already signals a non-destructive operation, and the description reinforces this by saying the report content is returned inline. It does not mention edge cases like size limits or failure modes, but no contradiction exists.

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 compact and front-loaded, with the core action and resource stated first, followed by format options and the JUnit recommendation. Every sentence adds useful information 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?

The description explains what the tool returns (inline report content) and mentions required project context, which is sufficient for a low-complexity export tool. It does not define the exact response schema, but that is not necessary given the inline-content statement and absence of an output schema.

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 already describes both parameters with defaults and types. The description adds meaningful context for the format parameter, especially the JUnit CI use case, and notes that testRunId is a public Guid, going slightly 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?

Clearly states the action 'Export a test run as a report' and distinguishes itself from related read/report tools by explicitly listing supported formats and the CI-oriented JUnit use case. The resource and output type are unambiguous.

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?

Provides specific guidance on when to choose the JUnit format for CI systems and notes that project context is required. It could more explicitly contrast with sibling tools like get_test_run or get_test_results, but the purpose is still clear enough for selection.

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