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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is covered. The description adds value by inventorying what the response contains (including custom fields and the next task), which matters because no output schema exists, but it says nothing about error behavior for an unknown id or any access restrictions.

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?

A single tightly-packed sentence with the return payload front-loaded and the underlying endpoint (GET /deals/{id}) appended for traceability. No filler, no restatement of the title.

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 read-only, one-parameter lookup whose safety hints come from annotations, the description is nearly complete, and the field inventory partly compensates for the absent output schema. A note on 404/not-found or missing-permission behavior would close the remaining gap.

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?

With a single parameter and 100% schema description coverage ('Pipeline CRM deal id.', positive integer), the schema already carries the semantics. The phrase 'by id' is consistent with the schema but adds no format or sourcing detail beyond it, so the baseline of 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 and resource ('One deal by id') and enumerates the returned surface (owner, company, stage, status, loss/won reasons, tags, custom fields, next task), which cleanly separates it from list_deals and the sibling get_company/get_person tools. It stops short of naming an alternative or restating the id scope, so it is clear but not maximally differentiated.

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?

There is no when-to-use or when-not-to-use guidance; the description never says to prefer this over pipelinecrm_list_deals when the id is unknown, nor mentions prerequisites such as valid authentication or an existing deal. Usage must be inferred entirely from the tool name and the single required id.

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