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

Annotations already establish readOnly, idempotent, and non-destructive behavior, but the description adds genuinely useful flow context: it charges nothing, returns specific fields (creditAmount, quoteToken, approvalExpiresAt), approval occurs in-chat with no link, and it explicitly handles the empty case without falsely claiming completeness. It does not cover rate limits or token validity semantics, keeping it short of 5.

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 core purpose and then packs the behavioral details efficiently. Most sentences earn their place, though 'Creating an artist stays free' is slightly tangential to quoting a reference pack.

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 needn't enumerate return values, yet it lists them anyway for clarity. It covers both kinds, the no-charge guarantee, the approval flow, and the empty-result behavior, so an agent has enough to invoke it correctly; only the confirm handoff is left implicit.

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%, so the parameters (including the photo_pack/look enum and lookDescription) are already well documented. The description reinforces the meaning of the two kinds but adds no syntax or format detail beyond the schema, making the baseline 3 correct.

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 ('Prices') and resource (the artist's missing reference views via photo_pack, or invented look via look), and even notes the price matches what the Brix36 app shows. An agent can distinguish this quoting tool from studio_artist_reference_pack_confirm without opening either schema.

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 clarifies this is a no-charge quote and that approval happens in-chat rather than via a link, which implies the confirm step follows. However, it never names the sibling studio_artist_reference_pack_confirm as the tool that acts on the returned quoteToken, leaving the when-to-use-next mapping to inference.

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