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

Annotations already indicate a write operation (readOnlyHint=false), non-idempotence, and non-destructive behavior. The description adds significant context beyond annotations: it costs 1 credit, refunds on failure, requires a live key file, and explains the specific error condition. This gives the agent a clear operational model.

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?

Three dense sentences, front-loaded with the core purpose, then constraints, prerequisites, and cost. Every sentence earns its place; no filler or repetition of schema details.

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 low-complexity tool with one parameter, no output schema, and rich annotations, the description covers the prerequisite, usage constraints, cost, error semantics, and expected effect. An agent has everything it needs to call this tool correctly.

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 input schema already describes the urls parameter well (full URLs, same host), and coverage is 100%. The description adds value beyond the schema by specifying the max 1000 URLs per call and clarifying that URLs can represent changed/new/deleted states, which informs how the parameter should be populated.

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 states a specific action (submit changed/new/deleted URLs to IndexNow) and the resource (IndexNow, search engines). It clearly distinguishes this from the sibling provision_indexnow_key by identifying itself as the submission step, so an agent can tell them apart.

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 explicitly says when to use the tool (for changed/new/deleted URLs), sets the prerequisite (key file must be live, call provision_indexnow_key first), and gives hard constraints (same host, max 1000 URLs). It also provides the meaning of the failure condition indexnow_key_not_verified, which is actionable routing guidance.

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