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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds real value beyond that by noting the data is 'Credential-free' (no auth needed) and 'normalized,' which tells the agent what kind of data to expect. It stops short of rate limits or error behavior, so not a 5.

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?

Front-loads the purpose and returned fields in one sentence, then gives the id note, then the sibling pointer. Mostly efficient, though the trailing 'Use discogs_release to get a Discogs release' is weakly relevant and reads as filler for a label tool.

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?

An output schema exists, so return values need not be explained, and the description covers the resource, its fields, the id format, and the credential-free nature. For a single-required-parameter lookup this is essentially complete, with only the sibling cross-reference being imprecise.

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%, with the id parameter already documented as 'Discogs label id, e.g. 895.' The description merely restates the same example verbatim, adding no syntax or format detail beyond the schema, so baseline 3 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?

States a specific verb and resource ('Returns a normalized Discogs label profile') and enumerates the returned fields (profile text, contact info, parent label, sub-labels). It does name a sibling (discogs_release), but that is not the most confusable neighbor (discogs_label_releases), so the sibling differentiation is only partial.

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?

Usage is implied rather than stated: 'Credential-free official Discogs database data' signals context, and 'Use discogs_release to get a Discogs release' points elsewhere, but there is no explicit when-to-use/when-not guidance for label lookups versus discogs_search or discogs_label_releases.

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