Get contact by ID

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

The annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is known. The description adds no behavioral information such as return format, error conditions, or the effect of the 'with' parameter. However, for a simple get operation, this is acceptable and not contradicting.

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, grammatically simple sentence that immediately conveys the core function. No unnecessary words or repetition. It earns perfect marks for conciseness.

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 low complexity, the lack of output schema, and the presence of annotations, the description is mostly adequate but leaves the 'with' parameter unexplained. The return data structure is not described, which could matter for downstream use. It is a minimal viable description with clear gaps.

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 schema documents 'id' as 'Contact ID', but the 'with' parameter has no description and the tool description does not clarify it. With 50% schema coverage and no additional explanation in the description, the agent is left guessing what 'with' accepts. This is a significant gap.

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 'single contact by ID'. It distinguishes from sibling tools like list or create by focusing on a single record retrieval, though it doesn't explicitly name alternatives.

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 vs alternatives like kommo_contacts_list. The implied usage from the name is not necessarily enough; a clearer note about using it when you have a specific contact ID would help. There are no exclusions or alternative recommendations.

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