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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is fully covered structurally. The description adds the underlying REST endpoint, which is mild context but not behavioral disclosure — it says nothing about how pagination behaves (page size, total counts) despite exposing a page parameter, nor about result caps or ordering.

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 sentences, zero filler, with the core definition front-loaded and the practical narrowing options second. The parenthetical gloss is compact and high-value rather than redundant.

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 read-only list tool with complete schema documentation, full annotation coverage and no output schema, the description covers what the tool is and how to narrow it. The one substantive gap is pagination semantics — a page parameter exists but neither description nor schema says how large a page is or how to know when to stop — so it is strong but not airtight.

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%, and the schema already explains that 'filter' matches part of the name and 'tags' matches any supplied tag, so the description's 'optionally narrowed by a name filter or by tags' adds no meaning beyond it. This is the baseline-3 case where the schema carries parameter documentation.

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?

A specific verb+resource ('List the organization's groups') with a genuinely useful gloss — 'which devices see which forms' — that explains what a group represents in the domain, something neither the name nor title conveys. It stops short of explicitly distinguishing itself from sibling list tools like devicemagic_list_devices or devicemagic_list_forms, but the resource concept does the disambiguating implicitly.

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 says the result can be 'optionally narrowed by a name filter or by tags', which implies when to supply those parameters, but it never states when this tool should be chosen over a sibling, nor any exclusions or prerequisites. Usage is inferable rather than stated.

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