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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description adds the meaningful access-control nuance that results are limited to what the user is permitted to see. It says nothing about ordering, pagination limits, or result shape beyond what the schema states.

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?

Two tight sentences that front-load the core scope before the optional capabilities. No filler or repetition; only slightly short of ideal since the second sentence is a bare feature list.

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?

This is a simple read-only list tool with full schema coverage and clear annotations, and no output schema is needed. The description covers scope, filtering, and pagination adequately; only guidance about defaults and result ordering is absent, which is minor.

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 description coverage is 100%, so page, limit, and search are fully documented in the schema. The description's mention of keyword search and pagination merely restates those parameters without adding format or edge-case detail, so the baseline of 3 applies.

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 and resource ('List all Test Manager projects') plus an authorization scope ('the authenticated user is allowed to see'). An agent can distinguish it from write-oriented siblings like tm_create_project or tm_update_project, though it is not differentiated from other tm_list_* readers such as tm_list_folders or tm_list_modules.

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 identifies supported capabilities ('keyword search and pagination') but gives no guidance on when to choose this tool over alternatives such as tm_get_test_runs or tm_list_folders, nor any prerequisites or exclusions. Usage is only inferable from the tool's name.

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