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

With no annotations provided, the description fully carries the behavioral disclosure burden. It explicitly warns that the submission is final, cannot be edited/recalled/deleted, delivers to a monitored human inbox, and that retrying sends a duplicate. It also discloses that nothing is stored and the enquiry becomes an email, which is valuable beyond the schema.

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?

Every sentence carries meaningful warnings or guidance, and the most critical information (finality, retry risk) is front-loaded. It is slightly longer than necessary because the permanence is emphasized twice ('cannot be edited, recalled or deleted' and 'becomes an email and nothing else'), which prevents a 5.

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 high-stakes, irreversible submission tool with no output schema, the description is thorough: it explains finality, retry consequences, delivery destination, data handling, and budget exclusion. It also covers parameter usage sufficiently, so the agent has the full context needed to invoke it safely.

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 a little guidance like 'Give the company or product website in company' and 'say what needs building in brief,' but these mostly restate the schema's own descriptions. It does not significantly extend parameter meaning beyond 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?

The description clearly states the tool's function with a specific verb and resource: 'Send a project enquiry to Dynomatix — the same form the site's enquiry page submits.' It distinguishes from the sibling submit_application by specifying 'project enquiry' and describing the enquiry page, so an agent can tell this is for project inquiries, not job applications.

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 strong usage guidance: confirm details before calling, do not call twice, and ask for budget on the call rather than here. However, it does not explicitly name alternative sibling tools like submit_application, so it falls short of full alternative-tool guidance.

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