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

No annotations are provided, so the description carries the full burden of behavioral disclosure. 'get CRM deal.' does not explain the response format, error behavior, authentication requirements, or side-effect-free read behavior. It adds no behavioral context beyond what the tool name already implies.

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?

The description is extremely short and front-loaded, but this is under-specification rather than effective conciseness. It contains no filler, yet it also fails to provide useful context beyond the tool name.

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 tool with two required parameters, no annotations, and no output schema, the description is insufficiently complete. It does not mention return value shape, not-found behavior, or the role of organization_id, leaving an agent to infer most behavior from the name and parameter names alone.

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% for both required parameters, reaching the high-coverage baseline. However, the schema descriptions are just 'deal_id' and 'organization_id', and the tool description adds no extra meaning about why both are required or how they relate. The baseline of 3 applies, but the description itself contributes no parameter clarity.

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 states a clear verb and resource: 'get CRM deal.' It unambiguously identifies the operation as retrieving a single CRM deal, and the singular 'deal' distinguishes it from list-style operations. It does not explicitly describe how it differs from sibling tools, but the core purpose is not vague.

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?

The description gives no guidance on when to use this tool versus alternatives like commsharbor_crm_deals_list, commsharbor_crm_deals_update, or commsharbor_crm_deals_delete. There are no prerequisites, exclusions, or scenario-based selection cues.

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