runFullSuite

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

Annotations already indicate readOnly, idempotent, and non-destructive behavior. The description adds that it produces a 'FullReport' with structure, but does not disclose details like error handling, timeout, or dependency on server. It is adequate but not thorough.

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 sentence that is front-loaded and contains no unnecessary words. It efficiently conveys the main action and output.

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 complexity (4 parameters, no output schema, no param descriptions), the description is insufficient. It fails to explain key parameters like target or specVersion, and does not mention the tool's read-only nature or any prerequisites. The description leaves critical gaps for correct usage.

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 has 0% description coverage, yet the description provides no explanation of any parameters (target, specVersion, oauth, suite). It only loosely references 'suites' but adds no meaning beyond the schema names and enums. This is a severe gap.

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 tool runs 'all (or selected) suites' and produces a 'FullReport', which distinguishes it from sibling tools that run specific suites (e.g., runJsonRpcCompliance, runTransportSuite). The verb 'Run' and resource 'suites' are specific, and the scope is clarified.

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 does not explicitly state when to use this tool versus its siblings. It implies it is for comprehensive testing via 'all (or selected) suites', but lacks guidance on when to choose specific suite tools or when this is appropriate (e.g., for CI vs debugging).

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