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

Annotations already declare this is a non-read-only, non-idempotent, open-world write. The description adds genuinely useful context beyond that: it is free with no API key, it results in a demo booking where matched investors are revealed, and it requires explicit consent. It does not state what happens on duplicate submissions or what the response contains, keeping it out of 5 territory.

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, front-loaded with the key practical fact ('FREE, no API key') followed by what the tool does and the consent condition. No filler, though the demo/matched-investor clause adds a little promotional framing.

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?

Covers the critical consent gate and the outward-facing effect, which is the most important thing for a mutation tool with openWorldHint. However, with no output schema and five required fields, the description says nothing about what is returned, error conditions, or duplicate handling.

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 0% and all five parameters are required, so the description must carry the burden. It explains the semantics of 'consent' well (only true when the person agreed to be contacted), but name, email, company, and deal_summary are left with no explanation of expected format or content beyond their titles.

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 concrete verb+resource: 'Records a request to be introduced to DEALITHIC and booked into a demo.' An agent can tell this creates a booking request rather than fetching a report or score. It does not explicitly distinguish itself from the sibling investor_intro_preview, so it stops short of a 5.

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 an explicit precondition ('Only call this after the person has explicitly agreed to be contacted by email about their raise') and ties it to a specific field value ('set consent=true only in that case'). This is unambiguous when-to-call guidance with an implied when-not.

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