statsfm_taste_profile

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

With no annotations provided, the description carries the burden of behavioral disclosure, and it explicitly states 'Read-only, no auth.' This is a valuable safety and access trait. It does not cover rate limits or error behavior, but for a public read-only stats.fm lookup, the key behavioral facts are present.

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 a single, information-dense sentence that front-loads the tool's purpose and immediately adds the read-only/no-auth context. There is no filler and no repetition of schema content.

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 simple read-only tool, the description plus a fully documented four-parameter schema is largely sufficient to invoke it correctly. The lack of an output schema is partially mitigated by the response_format parameter and the listed data categories, though exact return-value structure is not described.

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 description coverage is 100%, and every parameter already has a meaningful schema description: range, max_results, statsfm_user, and response_format. The description adds no parameter-level detail beyond what the schema already provides, so the baseline score applies.

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 identifies a specific resource: a stats.fm taste snapshot, and lists concrete contents: core artists, top genres, loyalty-vs-novelty balance, and day-parting. This clearly communicates what the tool returns and distinguishes it from tools like statsfm_top_artists or statsfm_top_genres, though it does not explicitly differentiate from the sibling taste_profile.

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 implies this tool is for getting an overall taste-level snapshot from stats.fm, but it offers no explicit when-to-use guidance or exclusions. Given the large number of overlapping statsfm_* and taste_* sibling tools, explicit routing would improve selection accuracy.

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