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

Goes beyond the annotations: it discloses that a reference number is returned and that the studio usually responds within one business day. The consent gating and the requirement for genuine contact details are additional behavioral context. It does not mention that repeated submissions create separate requests (consistent with idempotentHint=false), which would have earned a 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?

Three compact sentences with the action and the critical 'ask first' constraint front-loaded. Minor redundancy with the schema's field descriptions (e.g., 'describe the project in message'), but nothing that wastes the reader's time.

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?

There is no output schema, and the description fills that gap by naming the return value (reference number) and the expected turnaround. With ten parameters and no annotations about permissions, the consent precondition is well covered. A brief note on whether submission is fire-and-forget or whether follow-up is needed would make it fully complete.

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 the baseline is 3. The description adds operational meaning beyond the schema: it specifies that the name must be the person's real name, that phone or email is the contact path, that the project goes in message, and, crucially, the timing rule for consent. This raises it above baseline, though it does not explain optional fields like project_type or due_date.

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 ('Send a quote request to the studio') and ties it to a familiar analogue ('like the site's quote form'). This is clearly distinguishable from every sibling, which are all read/list/search tools, without needing to open a 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?

Gives concrete preconditions: ask the person first, use only their real name and phone or email, and set consent true only after they agreed. It stops short of naming an alternative path (e.g., what to do if the person hasn't consented), so it is clear context without explicit exclusions.

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