Get my MAL profile

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

Annotations already mark the operation as read-only and open-world, so the description does not need to restate safety. It adds useful behavioral context by requiring an active MyAnimeList login and by clarifying the anime-only limitation of the underlying API, which goes beyond what annotations or the empty schema convey.

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 concise sentences with no filler. The core purpose is front-loaded, and the login requirement and anime-only limitation are stated in a compact, structured way that earns every word.

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 has no parameters, an output schema is present, and annotations cover the read-only and open-world nature, the description provides the essential remaining context: auth requirement and the deliberate absence of manga stats. Nothing required for correct invocation or selection is missing.

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 schema description coverage is 100%, so there are no parameter meanings to clarify. With no parameters, the baseline is 4 since the description has no additional parameter burden to carry.

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: the logged-in user's MyAnimeList profile and their anime watch-status statistics. It explicitly narrows the scope to anime-only and distinguishes it from any manga-related tool, so an agent can identify it unambiguously among the many sibling tools.

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 states when to use it (for the logged-in user's profile and anime stats) and the prerequisite of a MyAnimeList login. It also explains that this tool is not for manga statistics because the official API has no such field and no tool exists for it, effectively providing a clear exclusion even without naming a specific alternative.

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