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

Annotations already declare the write/open-world/non-idempotent profile. The description adds real value on top: it discloses that a fit check gates the outcome, that a booking link is returned only when it fits, and that the supplied name, email and company are transmitted to Ruzora. It does not mention the buyer_token prerequisite or error behavior, which the schema covers.

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 tight sentences that front-load the audience and intent before the mechanics. Minor marketing padding ('fixed price, milestones') is the only waste, but it does convey commercial context cheaply.

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 9-parameter, no-output-schema lead tool, the description covers the key unknowns: it tells the agent a booking link is the return value and that fit is conditional. The buyer_token prerequisite is left entirely to the schema, and the not-a-fit path is only implied, keeping it just short of 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 description coverage is 100%, so every parameter, enum value, and the buyer_token flow is already documented in the schema. The description only echoes 'budget, timing' and 'name, email and company' without adding format or validation meaning, so baseline 3 applies.

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 names a specific action (request a scoping call), the provider (Ruzora's Software Factory), and the two qualifying intents (new build, rescue). It is clear what the tool does, but it never distinguishes itself from the sibling create_factory_inquiry, leaving that routing decision to inference.

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 gives clear target-audience context ('anyone who wants an app or software built, or a failing app or agency project rescued') and states the qualifying condition (fit on budget/timing). There are no explicit exclusions or named alternatives, so it stops short of full routing guidance.

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