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

Annotations already declare readOnlyHint=true, openWorldHint=true, destructiveHint=false, so safety is covered. The description earns credit by disclosing the returned attributes (account type, job title, status, last login) and the underlying GET /users endpoint, which matters since there is no output schema; it omits any mention of pagination limits or auth scope.

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 short sentences, front-loaded with what is returned and followed by the practical use of the ids. No filler or redundancy with the title.

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 nine optional filters fully documented in schema and safety fully covered by annotations, the description's remaining job is telling the agent what comes back and why it cares — which it does via the field list and the work-order assignment hint. Only return-shape detail and paging expectations are left implicit.

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%, including enum values for account_type and paging semantics for limit/offset, so the schema carries parameter meaning. The description adds nothing param-specific beyond naming the account-type concept, so baseline 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 UpKeep users') plus the concrete population it returns (technicians, admins, requesters) and the useful fields. The verb 'List' paired with the sibling 'upkeep_get_user' makes the retrieve-one vs. retrieve-many split unambiguous.

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?

'Use the ids to assign work orders' gives one concrete downstream use, which is real guidance beyond the name. However, it never says when to prefer upkeep_get_user for a single lookup or when to page instead of filtering, so alternatives remain implicit.

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