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 nothing beyond that — no note about what the label profile contains, whether data is cached, or how it relates to the releases endpoint. With annotations carrying the full behavioral load, a terse noun phrase contributes almost no extra context.

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?

It is a single three-word fragment with zero waste, but it is under-specified rather than genuinely concise — there is nothing to front-load because no information is given. Three words is not a sizing problem, it is an information problem.

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 annotations cover read-only behavior. However, for a one-parameter lookup in a family of six discogs tools, the description gives no basis for choosing this tool over discogs_release, discogs_artist, or discogs_search. It is minimally callable but not complete.

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 the single id parameter is documented in-schema with an example ('Discogs label id, e.g. 895'), so the baseline of 3 applies. The description adds no meaning beyond the schema.

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 'Discogs label profile' is essentially a restatement of the tool name discogs_label. It names a resource but no verb and no scope, so an agent cannot tell from the text alone whether it retrieves a label's metadata, its releases, or something else — that distinction has to come from the sibling name discogs_label_releases.

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?

There is no when-to-use guidance, no mention of the sibling tools (discogs_label_releases, discogs_search, discogs_artist), and no statement of prerequisites such as needing a label id obtained elsewhere. The agent must infer the usage pattern entirely from the name and schema.

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