list_traffic_plans

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

Annotations already declare readOnlyHint=true and openWorldHint=true. The description adds an actionable behavioral detail beyond annotations: 'Токен не требуется' (no token required), plus the exact endpoint. This is useful context for invocation without contradicting the 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?

A single front-loaded sentence contains the resource, scope, endpoint, and auth requirement. Every word earns its place and no redundant information is present.

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 simple list-operation shape, complete parameter schema, and read-only annotations, the description is largely sufficient. It omits return-format details, but there is no output schema and the operation is simple enough that this is a minor gap rather than a blocking one.

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 100%, so the schema already documents both parameters. The description only reinforces the mapping of 'preset' to instance_id and 'location' to location, adding no new semantic details beyond the schema.

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 identifies a specific resource ('traffic tariff plans') scoped by preset and location, and includes the endpoint 'traffic_plans/list', which makes the list operation explicit. This clearly separates it from sibling tools like list_presets or s3_list_plans.

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?

It states the intended context: traffic plans for a preset in a location. However, it gives no explicit guidance on when to choose this tool over siblings such as get_preset_pricing or s3_list_plans, so usage is implied rather than directed.

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