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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the safety profile is covered. The phrase 'as Audora holds it' adds a small but real signal that this is a canonical read rather than a staged/derived view, which helps distinguish it from propose_profile. It stops short of describing return content or any auth or scope 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?

A single front-loaded sentence with no filler or redundancy. It is arguably over-compressed, but nothing in it is wasted.

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?

The tool is simple: one optional, fully documented parameter, read-only annotations, no output schema. The description is adequate for that surface but does not state what the profile contains or how a missing profile is handled, leaving minor gaps for an agent deciding whether this call answers its question.

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 'artist' parameter is documented thoroughly in the schema (conditional on label connection, required for artist tools, source of the ID). The description adds no meaning beyond that, 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 (the artist profile) and asserts it is the authoritative version Audora holds, which is a useful qualifier. But it supplies no verb and offers no differentiation from close siblings like propose_profile, update_profile, or whoami, so an agent cannot fully disambiguate from the text alone.

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?

The description gives no when-to-use guidance whatsoever. The only routing information (label vs. artist connection, when to pass 'artist') lives entirely in the schema's parameter description, so the description itself contributes nothing toward selecting this tool over propose_profile or update_profile.

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