Get label

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

Annotations already declare readOnlyHint=true and openWorldHint=true, covering the safety profile. The description's added value is the enumeration of returned fields (country, status, address, styles, founding date, sub-labels, parent), which partly substitutes for the missing output schema, but it says nothing about error behavior or what an invalid label_id yields.

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 extremely short and wastes no words, but it is a dangling fragment rather than a front-loaded sentence, so the brevity comes at the cost of stating the action. The field list is dense but not scannable.

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 single-parameter getter with no output schema, the field enumeration gives the agent a reasonable picture of the return payload. It still omits any statement of what the tool does and when to call it, which leaves the definition thin for its role among many sibling retrieval tools.

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%: the schema documents the single label_id parameter ('Label id (from a band or release)') and its exclusiveMinimum constraint. The description adds no further detail about the identifier, so the 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?

The description names the resource (record label) and enumerates the profile fields returned, which lets an agent tell it apart from get_artist, get_band, and get_album by resource. However, it is a noun-phrase fragment with no verb ('Get label profile...'), so the actual action is only implied by the tool name rather than stated.

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 label_id source being required, and no reference to any alternative sibling tool. The agent must infer from the name alone that this is the retrieval call for label entities.

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