kommo_get_lead

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

With no annotations, the description bears full responsibility for behavioral disclosure. It only mentions retrieving lead details and attaching notes, but does not confirm read-only nature, auth requirements, or any side effects. The tool name implies read access, but transparency is minimal.

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 concise with only two sentences, no redundant information, and front-loads the core purpose.

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 simple get tool with no output schema, the description adequately states that it returns complete details with contacts and optional notes. However, it leaves ambiguity about the exact response structure and does not mention that contacts are included by default.

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 coverage is 50% (lead_id lacks description). The description adds no new semantics for lead_id and merely repeats the note_limit information already present in the schema. It does not compensate for the undocumented lead_id parameter.

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 explicitly states 'Detalhe completo de um lead por id, com contatos' which clearly indicates getting a lead by ID with contacts, distinguishing it from sibling tools like kommo_search_leads or kommo_update_lead.

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 given on when to use this tool versus alternatives such as kommo_search_leads or kommo_get_events. The description only states what the tool does without any when/when-not or comparison context.

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