Get a user's profile

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

Annotations already provide readOnlyHint=true and openWorldHint=true, indicating a safe, read-only operation. The description adds behavioral context by specifying that it gets public profile without the need for prior search, but does not contradict annotations. Additional details about direct username acceptance enhance transparency without redundancy.

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 two sentences, front-loaded with the core purpose, and contains no filler words. Every sentence adds necessary information: what the tool does and how to use it effectively.

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?

Given the single parameter, presence of output schema, and annotations, the description is complete. It covers the tool's purpose, parameter usage, and integration with sibling tools, leaving no gaps for the agent to infer.

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% with a description for the 'user' parameter. The description adds value by clarifying that the tool accepts an exact username directly and provides guidance on when to use search_user for partial names, going beyond the schema description.

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 verb 'get' and the resource 'AniList user's public profile', listing specific fields (name, about text, avatar, donator status). It distinguishes itself from siblings by noting that it accepts an exact username directly, implying no need for search_user first, which contrasts with sibling tools like search_user.

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 explicitly provides when-to-use guidance: 'no need to call search_user first unless you only have a partial/fuzzy name and need to look up the exact one.' This clearly states when to use this tool and when to use an alternative (search_user).

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