tochka_upd

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

Annotations only include openWorldHint: true. The description adds that the tool returns documentId and signURL and defaults to 'schfdop' function, but does not disclose side effects, permissions, or error behaviors. It does not contradict annotations.

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 structured with a clear purpose statement followed by an argument list. It is somewhat lengthy but efficient, front-loading the key purpose. Minor redundancy ('same format as invoice') could be trimmed but overall well-organized.

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 12 parameters, 5 required, and an output schema exists (so return values are covered), the description explains all parameters and the return value. It is complete for a UPD creation tool, though could elaborate on validation or constraints.

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 0%, meaning the description provides the sole parameter explanations. The description lists each parameter with a brief but meaningful explanation (e.g., 'buyer_type: company or ip' and 'function: schfdop (invoice+primary) or dop (primary only)'), adding critical value.

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 it creates UPD (universal transfer document) and returns documentId and signURL. It specifies the default function ('schfdop') and distinguishes this tool from other document-related siblings by focusing on UPD creation.

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 explains the default and optional parameters but does not explicitly state when to use this tool vs alternatives. No when-not scenarios or prerequisites are mentioned, leaving the agent to infer usage context.

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