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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds real context beyond that: pagination behavior ('a page of'), the cost signal '1 request', and a disclosure of what is deliberately excluded (schemas, write rules).

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?

Three terse sentences, front-loaded with the scope and output summary, then the sibling routing, then the cost note. No filler; every clause carries information.

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?

An output schema exists, so return values need not be explained, and annotations cover the safety profile. However, for a 13-parameter listing tool the description never addresses the filter/order surface, which is a meaningful gap even if the schema partially covers it.

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 only 54%, and the six boolean filters (pinned, readonly, realtime, activated, indexable, protected) carry no schema description at all. The description says nothing about filtering, ordering, pagination parameters or the tag AND/OR semantics, so it does not compensate for the coverage gap.

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 (lists) with explicit scope: 'a page of the account's lists that this token can see'. It also previews the returned data (flags, tags, item counts) and distinguishes itself from get_list by naming what it omits. An agent can tell it apart from get_list, create_list and update_list without opening any schema.

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?

Explicitly routes the agent to get_list for schemas and write rules, implying this tool is the enumeration surface rather than the detail surface. There is no explicit when-not beyond that single routing note, so it stops short of a full 5.

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