indexnow

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

With no annotations, the description must carry the behavioral burden. It discloses a key prerequisite, the external pinging behavior, and the 'instant and quota-free' nature. It does not disclose failure modes, network response behavior, or consequences of an invalid/missing key.

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 tight sentences with no filler. The key requirement (<key>.txt at site root) is surfaced alongside the primary purpose, making it easy for an agent to parse and act on.

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 simple single-parameter tool with no output schema, the description covers the essential action and prerequisite. Minor gaps remain around URL limits, error handling, and how the key file requirement is validated, but nothing critical is missing for basic invocation.

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%, and the sole parameter is already well described as fully-qualified URLs. The tool description adds little beyond restating that URLs are for added/updated content, which is adequate but not additive.

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 identifies a specific verb ('Ping'), a specific resource ('IndexNow network'), and the intent ('URLs added or updated'). It clearly differentiates itself by naming unique networks, though it does not explicitly contrast with sibling tools like submit_urls.

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?

The description implies when to use it: when URLs have been added/updated and instant, quota-free notification to IndexNow is desired. However, it does not provide explicit guidance on when not to use it or what alternatives like submit_urls are better for.

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