indexnow_ping

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

Annotations already declare readOnlyHint=false and openWorldHint=true, so the agent knows this is a mutating, externally-reaching call. The description adds that submission goes to specific external engines, which is useful, but omits rate limits, auth needs, idempotency, or what a submission result looks like.

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 short sentences, zero waste, with the core action front-loaded and the Google caveat as a tight follow-up. Every clause 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?

No output schema and no rich annotations, so the description must carry the behavioral load. It conveys what the tool does and its external scope, but a mutating network tool typically needs more on auth, limits, or expected outcome, which is missing.

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 coverage is 50%, and the schema documents site and key while leaving urls/sitemapUrl without descriptions. The phrase 'given or from the sitemap' maps loosely to those two params and adds some meaning, but the description does not compensate for the coverage gap at 50%.

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 (submits) and resource (URLs) with a clear target (IndexNow/Bing, Yandex, etc.) and notes the two input modes (given URLs or sitemap). It is distinguishable from most siblings, though it does not explicitly contrast itself with submit_sitemap or indexnow_key.

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 'Google ignores IndexNow' note implies a usage constraint and helps frame relevance, but there is no explicit when-to-use guidance, no when-not-to-use statement, and no routing to alternatives such as submit_sitemap. Usage is only implied.

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