site

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

With no annotations, the description carries the full burden of behavioral disclosure. It clearly says nothing is bought, ordered, paid, or guaranteed, and it is free. It also states what the tool returns: who receives the details, the consent wording, and how the person confirms. This makes the tool's behavior transparent for an informational, zero-parameter tool.

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 compact and front-loaded with the key usage instruction 'Read first.' Every sentence adds relevant information: what the tool describes, what it is not, and what it returns. There is no filler or repetition of schema content.

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 zero-parameter informational tool with no output schema, the description is complete. It says what the output covers — submit_enquiry's behavior, recipients, consent wording, and confirmation method — and gives enough context for the agent to know why it exists and when to read it.

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?

The tool has zero parameters and the schema is empty, so the baseline of 4 applies. There are no parameter semantics for the description to clarify, and the description does not need to compensate for any schema gap.

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 the tool's job directly: it explains what submit_enquiry does on Arizona Roof Replacement Cost. It distinguishes this 'describe' tool from the action tool submit_enquiry and makes plain that no purchase or guaranteed quote is involved. A reading agent can confidently tell this apart from its siblings.

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?

The opening 'Read first' is an explicit usage signal: this tool should be used before interacting with submit_enquiry, because it explains the enquiry process and consent details. It gives clear context for when to use it, though it does not explicitly name alternatives or state when not to use it.

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

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

No annotations exist, so the description carries the full behavioral burden. It does well by enumerating the exact returned attributes and making the mental model explicit: the field keys returned here are the keys for submit_enquiry. It does not discuss output shape or pagination, but for a parameterless read-only metadata query these are minor omissions.

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 two concise sentences with no filler. The first sentence front-loads exactly what the tool returns, and the second adds the actionable usage instruction. Every clause contributes.

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 simple, parameterless metadata tool with no output schema, the description is complete: it specifies the scope of results, the fields available, and how the result should be used with submit_enquiry. There are no required preprocessing steps or hidden constraints to disclose.

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?

There are no parameters, so the schema fully covers input semantics; the description has no parameter behavior to add. The only extra semantic guidance, the instruction to key submit_enquiry answers by field key, relates to output usage rather than parameters.

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 clearly identifies the tool's resource and content: every field of the Arizona Roof Replacement Cost enquiry, including key, label, type, required flag, help text, and options. It is specific about what is returned, but it never explicitly contrasts itself with the sibling enquiry_describe, so the differentiation is left largely to the name and title.

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?

The second sentence gives direct guidance: pass answers to submit_enquiry keyed by field key, which tells the agent why it would fetch this data. It does not formally state when to use this tool instead of enquiry_describe, but the submission-related instruction provides clear practical context.

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

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

With no annotations provided, the description carries the full burden and does so well: it discloses the two-step workflow, validation behavior, confirmation token requirement, consent meaning, email delivery, and the click-before-provider-visible condition. This gives an agent a realistic model of side effects and sequencing.

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 longer than average but every part serves a real purpose: the disclaimers, the exact consent text, and the sequential steps. It is front-loaded with the critical 'not a purchase' warning and then proceeds logically, though it could be slightly tightened with clearer step separation.

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 two-step stateful tool with three parameters and no output schema, the description is remarkably complete. It explains the required sequence, what happens after submission, and the condition before providers see the enquiry. An agent has enough information to call the tool correctly on both steps.

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?

The input schema already documents all parameters with 100% coverage, so the baseline is 3. The description adds meaningful process-level semantics: answers must be keyed by field key from enquiry_fields, consent requires the exact quoted agreement, and confirmation must be the token returned in step 1 after the person approves the summary.

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 verb and resource: it submits an enquiry to Arizona Roof Replacement Cost and clearly distinguishes the tool from purchase or quote actions. The title adds 'not a purchase' and the body names the exact target, making it easy to differentiate from the sibling describe/fields tools.

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?

The description gives clear context for when to use the tool and sets expectations by emphasizing it is not a purchase or guaranteed quote. It also references enquiry_fields for keying answers, but it does not explicitly contrast this tool with its siblings or state when not to use it.

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