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

Adds substantial context beyond annotations: quoting is free, Soclo refuses to film if the real price moves past the quote, quotes can exist while speech is unready or unmeasured, and authored lines must not be rewritten. readOnlyHint=false is consistent with creating a quote record; "free" refers to spend, not to mutation, so there is no annotation contradiction.

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 price meaning, then layers prerequisites, return values, and approval conditions without wasted language. The extra sentences about speech readiness and preserving authored lines each carry operational value.

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 complex quote-before-render workflow with no output schema, the description explains prerequisites, return fields, ownership approval, and follow-up conditions. An agent has enough context to call it correctly and interpret the result.

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?

Adds important source semantics for projectId and revision by requiring them from a soclo_plan read whose phase is "ready." It leaves the optional speechFitMode parameter to the schema, which documents it adequately, so this is strong but not 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?

States a specific verb and resource: get Soclo's authoritative price for filming a ready storyboard. It distinguishes the tool from siblings by naming soclo_video_make and soclo_plan and by framing the quote as a pre-filming step.

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?

Gives explicit sequencing: quote before soclo_video_make and pass quoted figures back unchanged. It names prerequisites from soclo_plan, explains the price-protection behavior, and states the conditions for filming only when speechFit.makeReady is true and the owner approves.

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