Analyze Taste (raw data export)

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

Annotations already declare readOnlyHint and openWorldHint. The description adds value by detailing the no-analysis policy, format, grouping, sorting, and the fetch cap with warning line, which goes beyond annotations.

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 three sentences plus a format line, all front-loaded with purpose and key details. Every sentence adds value with no redundancy.

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 no parameters and good annotations, the description covers output format, sorting, grouping, and fetch cap warning. It lacks explicit mention of whether the list includes all watch statuses or just completed, but the context is sufficient.

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?

No parameters exist (schema coverage 100%), so the description focuses on output format and behavior. It adds significant meaning about the expected output, which is crucial for agent usage.

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 returns the user's entire anime list in a compact text format, explicitly says it performs NO analysis, and the title 'raw data export' distinguishes it from siblings like search_anime and get_my_anime_list.

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 says to use this when you need raw data for analysis and clarifies it does not perform analysis. It implies alternatives are analysis tools or model post-processing, but lacks explicit when-not-to-use guidance for specific sibling tools.

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