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

Annotations already cover readOnly/destructive/openWorld, yet the description adds real value: reading 'does not complete or approve a task' preempts a likely agent mistake, and 'unavailable data is an error, not an empty task list' defines failure semantics explicitly. It also disambiguates the two action kinds (open_url vs navigate), which is behavioral detail absent from the schema.

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?

Dense but front-loaded: the read+auth precondition comes first, then payload, then the non-mutating caveat, then error semantics. Every clause carries information, though the open_url/navigate fragment is telegraphic rather than smoothly integrated.

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 handling return shape and only one input parameter, the remaining agent needs are auth gating, mutation safety, action-type meaning, and error semantics – all of which the description covers.

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?

Only one parameter (artistId) with 0% schema description coverage, though the UUID format and regex constrain it heavily. The description only implies it via 'an artist's' and adds no meaning about where the ID comes from or whether it must be one the caller has access to.

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?

States a specific verb and resource ('Read an artist's platform Action Center') and enumerates the payload (revision, task states, steps, primary/secondary actions). No sibling tool overlaps with Action Center, so the lack of explicit differentiation costs little, but the tool distinguishes itself by content rather than by naming an alternative.

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?

Provides one precondition – 'after authenticated artist access' – which is genuinely useful gating, but gives no when-to-use/when-not guidance relative to other read tools like get_account_overview or get_campaign_readiness. Usage context is implied rather than prescribed.

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