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

Annotations already declare readOnly/idempotent/non-destructive, so the bar is lower; the description still adds real value by noting viewer-access checking per ID, that app-only workflows retain existing consent and spend controls, and an explicit non-effect list (no purchase, paid work, or account deletion). It stops short of describing rate limits or failure 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?

Front-loaded with the return content, then the ID-driven branching, then constraints and guardrails. Every sentence carries information, though minor jargon ('appOnlyActions with reasons') is unexplained and costs a bit of clarity.

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?

An output schema exists so return values needn't be spelled out; against that, the description covers access checks, branching behavior, and explicit non-effects. It is close to complete for a read-only navigation tool, omitting only edge cases like inaccessible-ID handling.

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%, so a 3 baseline applies. The description still adds meaning beyond the schema: it defines the no-ID default (account controls) and what supplying an ID adds (screens plus appOnlyActions with reasons), which the schema properties alone do not convey.

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: returns verified native-app navigation and privacy/support links, with account vs artist/project screens differentiated by ID presence. It does not explicitly name or contrast with the nearest siblings (studio_account_read, studio_artist_read, studio_projects_list), but the 'links/navigation' framing is distinctive enough for an agent to route correctly.

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?

Explains parameter-driven behavior well (no IDs -> account controls; artistId/projectId -> artist/project screens), which implies when each invocation shape applies. However it never names an alternative tool or states when NOT to use this, so the alternative-selection guidance is only inferred.

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