kommo_get_deal

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

Without annotations, the description carries full behavioral burden, but it only says 'Get a deal by ID'. It does not disclose error behavior (e.g., what happens if deal not found), permissions needed, or rate limits. No side effects are implied, but the minimal text lacks necessary context for safe invocation.

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 a single sentence that is efficient and directly states the purpose. It is not verbose, but it could include slightly more information without losing conciseness. However, it earns its place.

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?

Given the tool's simplicity (1 parameter, no output schema), the description is adequate but minimal. It does not mention the return format or that it's a read operation. While not critically incomplete, it leaves the agent to infer details from the tool name and schema.

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?

The parameter 'dealId' has no description in the schema (coverage 0%). The description adds no additional meaning beyond 'by ID', and the schema already indicates it's a number. The tool description does not explain how to obtain this ID or any format constraints.

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 clearly states the verb 'Get' and the resource 'deal', and specifies the method 'by ID'. It distinguishes well from siblings like 'kommo_list_deals' (list all) and other get tools for different resources.

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 guidance is provided on when to use this tool versus alternatives. For example, it does not mention that if you need multiple deals, you should use 'kommo_list_deals', or that if you need a lead, you use a different tool.

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