yandex_submit_recrawl_urls

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

No annotations provided, so description carries burden. The main description is minimal, but the parameter description for 'confirmed' discloses that it spends Yandex recrawl quota, providing some behavioral context. However, other behaviors (e.g., error handling, quota exhaustion) are not mentioned.

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 very short and to the point. However, the note 'Requires confirmed=true' is redundant with the schema's required field and parameter description, which slightly reduces efficiency.

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 mutation tool that consumes quota, the description is too brief. It lacks information on return values, error conditions (e.g., invalid URLs, quota exceeded), and post-submit behavior. No output schema exists to compensate.

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 has 100% description coverage, so the description adds no extra meaning beyond what is already in the schema. Baseline 3 is appropriate.

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 the action ('submit'), target ('Yandex recrawl queue'), and constraints ('up to 150 URLs', 'requires confirmed=true'). This distinguishes it from sibling tools that read the queue or check quota.

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 on when to use this tool versus alternatives like yandex_get_recrawl_quota or yandex_get_recrawl_queue. The description only states a requirement (confirmed=true) but doesn't explain prerequisites or context.

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