Get a user's complete profile and stats

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

Annotations already communicate readOnlyHint and openWorldHint, but the description adds meaningful behavioral context: account settings are returned regardless of authentication, and statistics may be stale due to AniList aggregation lag. These are non-obvious traits that help the agent anticipate edge cases.

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 concise and front-loaded with the core purpose, then adds usage alternatives, auth behavior, and a caveat. Each sentence earns its place with no redundancy, making it efficient for an agent to parse.

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 a single parameter and an output schema, the description covers all essential aspects: what the tool returns, how it differs from siblings, when to use it, and potential data staleness. There are no gaps for an agent to select and invoke it correctly.

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?

The schema already covers the parameter ('AniList user ID, or username'), so the baseline is 3. The description adds value by clarifying that an exact username works directly without needing search_user, and that partial/fuzzy names require a prior search. This extra guidance goes beyond the schema.

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's function: 'Get an AniList user's profile AND statistics in a single call'. It also explicitly distinguishes it from siblings by saying 'use this instead of calling get_user_profile and get_user_stats separately', making the unique value obvious.

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 direct usage guidance: when to use this tool vs. alternatives ('use this instead of calling get_user_profile and get_user_stats separately') and when not to need search_user ('no need to call search_user first unless you only have a partial/fuzzy name'). This is explicit and actionable.

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