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

Goes well beyond the readOnlyHint/idempotentHint annotations by disclosing the critical behavioral nuance that nothing is transmitted and the user completes submission out-of-band, plus a PII-handling restriction. This is exactly the context an agent needs to avoid treating it as a send action.

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, purpose front-loaded, followed by the no-send clarification and the PII guardrail. Every sentence earns its place with no redundancy.

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?

Despite having no output schema, the description explains what the tool actually produces (a link) and how it is consumed, covering the safety profile, the handoff workflow, and the content constraint. Nothing needed to call it correctly 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 the baseline is 3, but the description adds real semantic value: subject and message are prefilled into the form, and the message must not contain personal data like emails or phone numbers. Only the language parameter is left entirely to the schema.

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: creates a prefilled BitSpire contact-form link. The description immediately resolves the ambiguity of the name 'start_inquiry' by clarifying that nothing is actually sent, and easily distinguishes it from the read-only page/site/search 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?

Gives clear operating context: hand the link to the user, who adds name and email and submits it, plus a negative constraint about not embedding personal data in the message. There is no explicit when-not or named alternative, but the siblings are unrelated, so no genuine ambiguity remains.

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