Get file by UUID

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

Annotations already declare readOnlyHint=true and openWorldHint=true, covering safety and world interaction. The description adds the behavioral detail that it returns 'metadata' (not file content), which is useful. However, it does not disclose error behavior, authorization requirements, or what 'metadata' includes, leaving room for ambiguity.

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 two short sentences with no filler. It front-loads the core purpose and includes only essential information. Every word contributes to clarity.

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 (one required param, no output schema), the description adequately covers what it does and what it returns. It does not mention error cases or output structure, but the 'metadata' note gives a clear expectation. With annotations providing safety context, this is near-complete for a lookup tool.

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 defines a single 'uuid' parameter with no description, and the schema description coverage is 0%. The description clarifies that the parameter is the file UUID via 'by UUID', but does not elaborate on format, source, or how it relates to other file operations. For a single simple parameter, this is acceptable but not rich.

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 resource ('file metadata by UUID'), which distinguishes it from sibling tools like kommo_files_list or kommo_files_edit. It specifies the exact scope (metadata) and the key (UUID), leaving no ambiguity about its function.

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 provides no explicit guidance on when to use this tool versus alternatives. It does not mention that this should be used only when a file UUID is already known, nor does it suggest kommo_files_list for discovering UUIDs. No exclusions or prerequisites are stated.

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