Queue URL for re-crawl

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

Annotations declare readOnlyHint=false and destructiveHint=false, so the description's own contribution is the daily quota constraint (a rate limit), the returned task_id, and the follow-up workflow. It does not say what happens when the quota is exhausted or what errors surface, but it adds solid operational context beyond 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?

Front-loaded with the action, then constraints, then alternatives, in four tight sentences. The second quota sentence mildly repeats the parenthetical 'check get-recrawl-quota', which is the only bit of redundancy.

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?

With no output schema, the description correctly discloses the return value (task_id) and the handoff to get-recrawl-task, plus the quota gate. For a two-parameter enqueue tool this is complete.

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 both url and host_id are already documented with format hints in the schema. The description adds no syntax or format detail beyond that, making the baseline 3 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?

States a specific verb (enqueue) and resource (URL for Yandex re-crawl), and explicitly differentiates itself from siblings get-recrawl-quota and get-recrawl-task. An agent can distinguish it from every other recrawl tool without opening a schema.

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?

Gives an explicit when-to-use condition ('when the user asks Yandex to recrawl one URL and the daily quota still has room') and two explicit exclusions naming the correct alternative for each. Nothing is left to inference.

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