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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world, so safety is covered. The description adds behavioral value beyond that by disclosing what suiteId returns (an ordered set of items: tests + plans) and what parentSuiteId scopes to. It stops short of mentioning pagination or result limits, which would be the remaining 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?

Three compact sentences, each earning its place, with the default behavior front-loaded before the two parameter-driven modes. No redundancy or filler.

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 read-only listing tool with no output schema, the description covers scope and return content adequately. It does not address pagination or result volume, which is the only meaningful omission for a list operation.

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 100%, so the baseline is 3, but the description genuinely adds semantics the schema does not: that suiteId's result includes ordered items, and that omitting both parameters lists every suite. The interaction between the two parameters is clarified.

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?

States a specific verb+resource ('List the authenticated user's test suites') and then enumerates the three distinct modes of operation, so an agent can tell exactly what the tool returns in each case. It is clearly separable from siblings like test_suite_create, test_suite_add_item, and test_suite_run.

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?

Explicitly maps each parameter to a usage mode: suiteId for a single suite with items, parentSuiteId for direct children, and omitting both to list everything. This is a complete when-to-use-which-mode guide with no inference required.

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