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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safe-read profile is fully covered by structured data. The description adds the list of returned sections, but an output schema already exists, so that content is largely redundant rather than additive. No mention of auth, rate limits, or scoping behavior.

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 the invocation trigger placed first and the payload second. Every element earns its place, though the inline trigger-phrase list is slightly padded where one or two examples would have sufficed.

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?

With an output schema, safety annotations, and a fully documented single parameter, the description only needs to establish purpose and invocation context, which it does. It is complete for a simple read tool, with the minor gap of not routing against the many sibling get_* 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 coverage is 100% and there is only one optional parameter whose role is already documented in the schema. The example phrase 'bio for That Boy Hi Hat' weakly illustrates the artist parameter, but adds no format, matching, or defaulting semantics beyond what the schema states. 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 a specific resource (press kit) and enumerates its contents: label bio, artist bios, release info, brand assets, and press contact. The trigger phrases ('press kit', 'media assets', 'bio for X') make the retrieval intent unambiguous, though it never explicitly distinguishes itself from adjacent read tools like get_artist or get_label.

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?

It gives an explicit invocation condition ('CALL THIS when the user needs press materials') anchored to concrete user phrasings, which is stronger than typical implied usage. It does not, however, state when NOT to use it or which sibling to prefer for an artist-only bio request.

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