list_work_item_autotests

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds nothing further: no indication of result volume, pagination, whether unlinked or deleted autotests are included, or whether an empty result is an error. For a read tool with annotations, the bar is lower, but this adds literally zero behavioral context.

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?

It is certainly short, but brevity here is under-specification rather than economy: a sentence fragment with no verb and no front-loaded operational detail. Nothing is wasted, but nothing is earned either.

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 tool is simple (one required parameter, no output schema, no nested objects), so it should be easy to describe fully. Yet given the dense cluster of link/unlink/list autotest siblings, the definition lacks the minimum disambiguation an agent needs to select it confidently over list_autotest_work_items.

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?

There is a single required parameter whose schema description ('Work item UUID.') is fully documented at 100% coverage. The description adds no meaning beyond the schema, which is the expected baseline 3 when the schema carries the documentation burden.

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 is a noun fragment, 'Autotests linked to a work item,' that essentially restates the tool name rather than stating a verb and resource explicitly. It does not distinguish this from closely named siblings such as list_autotest_work_items (the inverse relationship) or unlink_work_item_autotests, leaving an agent to infer the direction of the query.

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?

There is no when-to-use guidance, no mention of when not to use it, and no reference to alternatives even though the sibling list contains several plausibly confusable tools. The agent must infer that this is the read-side counterpart of link/unlink operations entirely on its own.

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