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

Annotations already declare readOnly/idempotent/non-destructive, but the description adds behavior annotations don't cover: no star ratings, empty results are normal and must not be padded with invented endorsements. That's meaningful disclosure beyond the annotations, though it doesn't cover pagination or return shape.

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?

Terse and front-loaded: the read behavior is stated first, then the warning, then the chain and write counterpart. Every fragment earns its place.

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 full schema descriptions and annotations, the description covers the essentials: what it reads, that empty is valid, and how it relates to get_creator and endorse_creator. It could briefly mention sorting/pagination, but nothing critical is missing.

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 every parameter (userId, sort, limit, cursor) is described in the schema, including enum values and defaults. The description adds no parameter-level detail beyond the schema, so baseline 3 is appropriate.

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 states a specific operation: publicly reading relationship-endorsement text for a creator, with no star ratings. It doesn't perfectly distinguish from the sibling get_relationship or get_creator, but the 'no star ratings' and 'recommendation text' details are specific enough for an agent to understand the resource.

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?

It explicitly names the alternative workflow: use endorse_creator for writing recommendations, and form a composition chain with get_creator. It also warns that empty is normal and recommendations must not be fabricated, which gives explicit when-to-use and when-not-to-use guidance.

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