get_user_collection_value

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

No annotations exist, so the description carries the full burden. It discloses no behavioral traits such as being read-only, requiring authentication, rate limits, or data freshness. The mention of 'returns' weakly implies a read operation, but lacks explicit safety or side-effect disclosure.

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?

One concise sentence that communicates the core functionality without any fluff. Every word adds value, and the structure is straightforward.

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?

Although the tool is simple, the description is incomplete: it does not define what 'value' means (e.g., monetary, numeric rating, or item count). No output schema is provided, and there is no mention of pagination, sorting, or error conditions. Given the context of sibling tools like get_user_collection_items (which likely returns more data), the description fails to set expectations for what exactly is returned.

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 input schema has zero description coverage for the only parameter 'username', and the description does not clarify its meaning (e.g., Discogs username must be provided). It assumes the agent knows 'user' refers to a Discogs user. A more helpful description would explicitly state the parameter's role.

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?

Clearly states the tool returns the minimum, median, and maximum value of a user's collection. The verb 'Returns' and specific nouns 'minimum, median, and maximum value' precisely define the action and resource. Differentiates from sibling tools like get_user_collection_items or get_user_collection_folder, which focus on listing or folder structure.

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?

Implies usage for statistical value summaries, but no explicit guidance on when to use this tool versus alternatives like get_user_collection_items or other collection-related tools. Does not provide before/after conditions or examples of appropriate use cases.

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