Тарифы S3-хранилищ

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

Annotation contradiction: the description claims a read-only operation ('Returns a list'), but readOnlyHint=false indicates it may modify state. This is a serious inconsistency that undermines trust. No other behavioral context is provided.

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?

Two sentences, front-loaded with purpose, then usage guidance. Every word is useful; no fluff or repetition.

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 parameterless listing tool with no output schema, the description fully covers the return fields and a concrete use case. It is sufficiently complete for the agent to understand what the tool does and when to use it.

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 tool has zero parameters and the schema is empty, so baseline 4 applies. The description does not need to explain parameters and does not add any conflicting information.

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 explicitly states the tool returns a list of available tariffs for S3 storage, naming specific fields (id, disk size, price, class, location). It clearly differentiates from sibling bucket management tools like get_bucket or list_buckets.

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?

Provides explicit usage guidance: 'Use before create_bucket to get preset_id.' This tells the agent when to call it, but doesn't mention alternatives (e.g., get_allowed_presets) or when not to use, so it misses the full 5.

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