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

Annotations already supply destructiveHint=true, so the safety profile is partly covered. The description adds the underlying REST endpoint, which is useful context, but says nothing about permissions, what happens with invalid linked ids, or the fact that a new deal id is returned for chaining. No contradiction with the annotation.

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 compact sentences plus the endpoint, with the required field front-loaded. Minor redundancy in repeating that `title` is required, which the schema already enforces, but nothing bloated.

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 an 11-parameter mutation tool with no output schema, the description is thin: it does not describe the created object's return (id) that an agent needs to chain follow-up calls, nor pipeline/stage/visibility semantics. Adequate to invoke, but incomplete for a create tool.

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%, so every parameter is already documented. The description only restates that `title` is required and lists the linkable entities already present in the schema, adding no format or interaction detail (e.g., currency pairing with value). Baseline 3 applies.

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+resource ("Create a new deal") and identifies the required field, which is enough to separate it from create_person/create_activity/create_note siblings. It does not explicitly name an alternative, but the scope is unambiguous.

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?

"link it to a person/org/pipeline/stage/owner as needed" implies the tool is for creating deals with optional associations, but there is no when-to-use vs which-sibling guidance or prerequisites (e.g., needing existing person/org ids). Usage must be inferred.

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