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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, and the description adds substantial context beyond that: configurations are human-created in the UI (not via API), are organization-level and shared across all projects, and results are paged with a total count in the response. These are non-obvious behavioral traits an agent needs.

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?

Front-loaded with the core purpose, then dense, high-value sentences on the id distinction and paging. Slightly long, but nearly every sentence carries actionable information; the 'each test instance carries exactly one configuration' line is marginally less essential.

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?

With no output schema, the description still covers return behavior (total count, pagination) and the org-level scope constraint. Combined with annotations covering the safety profile, an agent has everything needed to call this correctly.

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 adds real semantic value: it warns that the TOP-LEVEL id (not nested environments[].environment_id) must be used as configuration_id, and clarifies run_type's kaneai vs manual meaning. Page/limit are only referenced generically ('page through them or raise limit').

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 (List) and resource (saved run Configurations) and defines what a configuration is (reusable platform/browser/OS/device setups). It also distinguishes itself from the sibling tools tm_create_test_run and tm_update_test_run by explaining that this tool is the source of the configuration_id those tools consume.

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?

Gives clear context: pass run_type to narrow by kaneai vs manual, and notes there is no project filter because configurations are org-level. It routes the agent to sibling tools for applying a configuration but doesn't state explicit when-not-to-use conditions beyond the implicit 'use tm_create_test_run to apply'.

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