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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds real behavioral context beyond that: pending/held photos retain their status, the app link carries consent and scan controls, and no scan/LLM/image generation is initiated. That is meaningful extra disclosure for a read tool.

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-loads the return payload in the first sentence, which is the right ordering. Four sentences, mostly earning their place, though 'The app link identifies consent and scan controls' is slightly opaque without more context. No redundant filler.

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 present, the description need not document return values, yet it still summarizes them and adds the non-obvious side-effect guarantee (no scan/generation starts). Combined with full annotation coverage, an agent has enough to call it correctly; only explicit sibling routing is missing.

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?

There is a single parameter with 100% schema description coverage, and the schema already explains that artistId comes from studio_artists_list/studio_artist_read and is used when casting a Film. The description adds nothing about artistId, so the schema does all the work and the baseline of 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?

States a clear verb (returns) and enumerates the specific resources: identity summary, published photo pack, pending screening, approved creative facts, and social-scan statuses. This is far more specific than a tautology and clearly separates it from studio_artist_dna_write. It stops short of naming a sibling tool explicitly, so it lands at 4 rather than 5.

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 line 'No scan, language model or image generation starts' usefully tells the agent this read does not trigger downstream generation, which is a when-not signal. However, it never says when to prefer this over studio_artist_read or studio_artist_dna_write, nor states any prerequisite (e.g. needing an existing artistId). Usage is implied rather than stated.

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