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

Annotations already declare readOnlyHint=true, and the description adds useful behavior beyond that: this is a public read, results contain no star ratings, and an empty response is valid so the agent must not invent endorsements. It does not describe pagination behavior or the exact response shape, but the added empty-state warning is valuable.

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 description is very compact and front-loads the core read semantics, with no wasted sentences. The arrow shorthand 'get_creator→推荐' is slightly cryptic, but the overall structure remains efficient and usable.

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 simple read-only list tool with complete schema coverage and a readOnly annotation, the description covers the essential purpose, read/write distinction, and empty-result behavior. It leaves return shape and pagination details to the schema and annotations, which is acceptable here.

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%, so the input schema already documents userId, sort, limit, and cursor. The description adds no parameter-specific meaning beyond the schema, which is the expected baseline when the schema carries the 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?

The description states a specific verb and resource: publicly read relationship recommendation text/endorsements, with no star rating. It also explicitly distinguishes this from the write-side sibling endorse_creator, so an agent can tell read vs. write apart without opening either 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?

It gives clear usage context by saying recommendations are written with endorse_creator, so this tool is for reading rather than writing. It also warns that an empty result is normal and recommendations should not be fabricated, though it does not give detailed guidance on when to prefer get_creator versus this endpoint.

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