Get User Manga List

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

Annotations already set readOnlyHint=true and openWorldHint=true. The description adds useful behavioral info: same paged shape as 'get_my_manga_list', plus 'user_name' echoed in response, and error conditions. No contradictions with annotations.

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 sentences, each adding value. The first sentence states the core purpose, the second explains shape similarity, and the third covers error handling. No fluff, front-loaded with key 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?

The tool has 5 parameters, no output schema, and moderate schema coverage. The description covers purpose, public list constraint, shape similarity, and error handling. It could mention pagination limits or return structure, but given annotations and siblings, it is sufficiently complete for an AI agent.

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 60%, meaning 3 of 5 parameters have descriptions in the schema. The description does not add new semantic details for parameters beyond noting shape similarity to another tool. With moderate schema coverage, the description provides minimal additional value for parameters, so a baseline score of 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 clearly states the tool fetches 'a page of ANOTHER MAL user's manga list' and specifies it only works for public lists. The verb 'fetch' and resource 'another user's manga list' are specific, and it distinguishes from sibling tools like 'get_my_manga_list' (own list) and 'search_manga' (search).

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?

The description provides context that the tool works only for public lists and mentions a common error (403) meaning the list is private or username doesn't exist. It implicitly suggests using this tool over 'get_my_manga_list' when accessing another user's list, though explicit alternatives are not named.

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