iiko: стоп-листы

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

The description does not disclose any behavioral traits beyond the endpoint. It omits whether this is a read-only query (despite POST), what it returns, whether authentication is needed, or any side effects. With no annotations provided, the description carries the full burden and fails entirely.

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 terse, but this under-specification is not appropriate conciseness. It is a noun fragment without a predicate, lacking essential context such as the action performed. It could be equally concise and informative with a verb.

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 2-parameter tool with no annotations and no output schema, the description is severely incomplete. It does not state what the tool does, when to use it, what it returns, or any side effects. Sibling differentiation is absent, making it nearly impossible to invoke correctly.

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 description adds no meaning to the parameters. Schema covers only organizationIds (50% coverage), leaving apiLogin undocumented. The description does not name or explain any parameter, so it fails to compensate for the 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 'Стоп-листы по организациям (POST /api/1/stop_lists)' identifies the resource (stop lists) and the endpoint, but lacks a clear verb such as 'get', 'list', or 'create'. It is distinguishable from siblings by noun phrase alone, but the intended action is ambiguous.

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 about when to use this tool over alternatives like iiko_organizations or iiko_request. There is no mention of prerequisites, typical scenarios, or exclusions.

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