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

Annotations already declare readOnly/idempotent/non-destructive, so the bar is low, and the description clears it by adding real behavior: 200-result batches, offset-based skipping, that 'more' carries the next offset, most-recent-first ordering, and the account-linking prerequisite. It adds value beyond the annotations, though it omits any rate-limit or failure behavior.

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?

The resource is front-loaded, but the whole definition is one run-on sentence with nested parentheticals, and the 'more gives the next offset' rule is stated once in the description and again in the schema. Accurate but harder to scan than it needs to be.

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 single-parameter read tool with an output schema, the description still covers ordering, page size, pagination continuation, returned fields, and the account-link prerequisite, leaving little ambiguity. It does not explain the tag-count portion's shape, but the output schema covers returns.

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% and the single offset parameter is fully documented there, including default 0 and the next-offset pointer. The description essentially restates the schema semantics with no extra syntax or format detail, 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?

Names a specific verb+resource (list the person's scores in their linked Cesure account) and enumerates the returned fields. It is distinguishable from read_my_score and search_catalog by the plural listing and account-scoping, though no sibling is named explicitly.

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?

States the prerequisite 'Needs the account linked,' which is useful context, but never says when to prefer this over search_catalog or read_my_score, nor when not to use it. Usage is only implied from the name and the plural listing.

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