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

Annotations already declare readOnlyHint=false, destructiveHint=true, idempotentHint=false, so the agent knows this is a non-idempotent write. The description's only behavioral content is the 'WRITE:' prefix, which merely restates readOnlyHint=false and adds no new information about permissions, side effects (e.g. source auto-creation), or reversibility.

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?

Two short fragments, operation type front-loaded, zero filler. It is arguably over-compressed for an 11-parameter write tool, but nothing in it is wasted.

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 write tool with 11 parameters and no output schema, the description omits what the call returns (deal id?), what side effects occur (source record creation), and what authorization or prerequisites are needed. The schema carries the parameter burden, but post-invocation expectations are left entirely unspecified.

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% and all 11 parameters are documented in the schema, so the baseline is 3. The description only echoes the buyer_id concept, adding no syntax, defaults, interdependencies, or format notes 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?

States a specific verb and resource ('create a deal') and clarifies the relational target ('for a buyer (a person or company)'). It is distinguishable from update_deal and get_deal, but it does not differentiate itself from the other create_* siblings beyond the resource name.

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?

No when-to-use guidance, no prerequisites (e.g. that buyer_id must reference an existing person or company record), and no pointer to alternatives such as teamgate_update_deal for modifying an existing deal. 'POST /deals' is endpoint trivia rather than usage guidance.

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