Get a user's profile

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

Annotations already indicate readOnly and openWorld, but description adds meaningful beyond-annotation context: explicitly states account settings are included for any user, not just the authenticated caller. This removes potential ambiguity about data accessibility.

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?

Four sentences, each serving a distinct purpose: scope, transparency detail, input guidance, and alternative tool recommendation. No redundancy or filler; concise yet information-dense.

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-only tool with an output schema, the description covers purpose, contents, special behavior, and alternatives. It is fully self-sufficient without requiring external context.

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 covers the parameter with 'AniList user ID, or username' (100% coverage). The description adds value by explaining that an exact username is accepted directly, eliminating the need for a preliminary search, which clarifies expected input.

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?

Description opens with a clear verb+resource: 'Get an AniList user's public profile' and enumerates specific contents (name, about, avatar, donator status, account settings). It differentiates from siblings by explicitly naming get_full_user_info and 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?

Provides explicit when-to-use guidance: states exact usernames need no search_user first, and suggests get_full_user_info when statistics are needed. Also clarifies that settings are not viewer-gated, so the tool is appropriate for any user.

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