get_label

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 usefully discloses that results include parent label and sublabel context, but says nothing about what happens with a missing/invalid label id or about rate/remote-lookup behavior implied by openWorldHint.

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?

A single front-loaded sentence with no filler; the problem is under-specification rather than verbosity. Nothing in the sentence is wasted, but there is very little of it.

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?

No output schema exists to explain return values, so the description must carry that burden and it only names two content elements. With two undocumented parameters and no error/miss behavior, an agent has clear gaps before calling it correctly.

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% and neither parameter is mentioned in the description. The required 'label_id' and the optional 'include_images' flag (which likely changes payload size) are left entirely undocumented, so the description does nothing to compensate for the schema gap.

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?

Names the resource ('label profile') and qualifies its contents (parent label and sublabels), so an agent knows what kind of record comes back. It lacks an explicit verb and never names the neighbouring get_label_releases, but the 'profile' framing does implicitly separate it from a release listing.

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 statement of when to call this versus get_label_releases or the artist/release getters that sit alongside it in the sibling list. The agent must infer the distinction from the noun 'profile' alone.

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