Block places

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

Explicitly states 'Destructive', requires confirm=true and Partner-Name header, and explains indefinite block when 'to' omitted. No annotations provided, so description carries full burden and does well.

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 pack purpose, endpoint, destructive warning, required items, tags, and indefinite behavior with no filler. Well front-loaded and every word earns its place.

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?

Covers key behavioral aspects and requirements, but lacks details on success response, scope (all delivery types), and links to related tools (e.g., block_status). Still adequate given no output schema.

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 covers parameters descriptively (67% coverage), but description adds crucial info: Partner-Name header (not in schema) and clarifies indefinite block for 'to' (partially redundant). Overall adds meaningful value beyond 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?

Clearly states 'Block restaurant(s) in Yandex Eats (POST /block)', providing a specific verb and resource. The sibling tool 'unblock_places' indicates differentiation, though not explicitly mentioned.

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 context: destructive action, required confirm=true, Partner-Name header, allowable tags, and indefinite behavior if 'to' omitted. However, lacks explicit when-not-to-use or comparison to alternative tools like 'unblock_places'.

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