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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is partly covered. The description adds real behavioral value beyond that: "No credits are spent" and that manual edits/export are free, which is precisely what an agent needs to know before deciding to quote vs. generate.

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?

The critical fact (no credits spent) is front-loaded, followed by a compact per-kind price list. Every clause carries information; there is no 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?

For a read-only quoting tool with no output schema, the description supplies the cost model, the no-spend guarantee, and the count prerequisite. It stops short of saying what the returned quote actually looks like, but that gap is minor given the tool's simplicity.

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?

With schema description coverage at 0%, the description carries the burden and largely delivers: it maps enum meanings to costs (outline 2, carousel 2 + 10 per slide, cover/illustration 10) and flags that carousel requires count. It does not restate count's 2-10 bounds, so the mapping is nearly but not fully complete.

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 states a specific action (get the exact credit charge) and resource (AI generation) and implicitly separates itself from the sibling studio_generate by stressing that no credits are spent. It stops short of naming the generate tool it precedes, but an agent can still tell the two apart.

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?

"Get the exact credit charge before generating" gives a clear usage context (call this first, then generate), and "requires count" states a prerequisite tied to one pricing branch. It does not explicitly name the alternative tool or say when a quote is unnecessary.

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