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

Annotations already declare read-only, non-destructive, idempotent, and closed-world behavior. The description adds important workflow context beyond annotations: the quote is free and makes no picture, approval is required before editing, and backup model use is strictly constrained.

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 description is front-loaded with purpose and then adds operational constraints in a compact sequence. Every sentence carries useful information with 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 quote/preflight tool with no output schema, the description supplies the return content ('price and pricingVersion'), the required approval step, and the backup model rules. Nothing essential for correct invocation 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?

Schema coverage is 100%, so baseline is 3. The description adds cross-call constraints not captured in individual parameter schemas: 'Use the same editor and picture tier for the quote and edit' and 'retain the reviewed photos and gptRefusalRequestId'.

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 ('Get the current account price and pricingVersion') and states the scope ('to edit a photo'). It explicitly distinguishes itself from the edit action by naming soclo_image_photo_edit as the operation that follows after approval.

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 explicit when-to-use guidance: call before soclo_image_photo_edit, show the price, wait for approval. It also clarifies that the call is free and changes nothing, and gives a specific backup condition for Nano Banana Pro after a GPT edit refusal.

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