discogs_get_label

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

With no annotations provided, the description must disclose behavioral traits. It only says 'Get... by ID' but omits critical details: whether authentication is required, what the return format is, rate limits, or error handling (e.g., invalid IDs). This is a significant gap for a tool that likely has API constraints.

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 very concise (one sentence, 7 words). However, conciseness comes at the expense of completeness. For a simple get-by-ID tool, minimal wording can be acceptable, but here it omits essential details. It is not verbose, but it is under-specified.

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 the tool's simplicity (2 params, no output schema, no annotations), the description should still provide enough context for correct invocation. It fails to describe the return value, error behavior, or parameter specifics. The agent has insufficient information to use the tool confidently.

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 0% per context signals, so the description must compensate. It does not explain either parameter: label_id (e.g., format, range) or api_key (when/why to use). The description adds no meaning beyond the raw schema fields.

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 verb 'Get' and resource 'Discogs record label', and specifies the identifier 'by ID'. This distinguishes it from sibling tools like search (discogs_search_releases) or other entity-specific tools (discogs_get_artist). The purpose is unambiguous.

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?

No guidance on when to use this tool vs alternatives. For instance, it doesn't mention that one should search for a label ID first if unknown, or that api_key may be needed for certain labels or rate limits. The description lacks context for appropriate invocation.

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