Get the logged-in user's profile

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

Beyond the readOnlyHint annotation, the description discloses the login requirement ([Requires login]) and explains that this tool returns the authoritative current values needed for full-replace updates. This is valuable behavioral context that annotations alone do not provide.

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 front-loaded with the core purpose and then provides rich, relevant usage caveats. While long, every sentence carries operational significance, though it could be tightened by moving some update_user details to that tool's own description.

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 tool's simplicity (no params, read-only) and the rich output schema, the description covers the purpose, auth prerequisite, workflow context, and specific scenarios where this tool is essential. It's complete for an AI 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 tool has zero parameters, and the description clarifies that the target account is determined via login state rather than a parameter. It explains how the authoritative identity is established (via login_anilist/ANILIST_ACCESS_TOKEN), adding meaning beyond the empty 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 gets the profile of the currently authorized AniList account, using a specific verb and resource. It explicitly differentiates from other user-focused tools (e.g., get_user_profile) by targeting the authorized account and ties it to login_anilist/ANILIST_ACCESS_TOKEN.

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 provides explicit when-to-use guidance: to confirm which account is connected, and as the authoritative prerequisite fetch before update_user calls involving specific fields. It even explains the array-replacement and positional-index risks that necessitate reading current values first, which strongly steers usage toward this tool.

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