Enable/Disable IndexNow

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

Annotations already declare idempotentHint=true and destructiveHint=false, covering the safety profile, and the description usefully adds the default state and the site-level scope. It does not say what disabling actually stops (polling, future changed-page submissions, in-flight work) or whether any permission is required, so the added behavioral value is modest.

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?

One sentence, front-loaded with the action and resource, with the default state appended where it is most useful. Nothing is wasted or repeated from the schema.

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 one-boolean, idempotent, non-destructive toggle with a fully documented parameter and no output schema, the description supplies what an agent needs plus the default-state caveat. Only the effects of disabling remain unspecified, a minor gap for a tool this simple.

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 single parameter is documented at 100% coverage in the schema, including the meaning of true ('submit changed pages automatically') and false ('stop'). The description adds no syntax, format, or edge-case detail beyond that, so baseline 3 applies.

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 gives a specific verb pair (turn on/off) and a specific resource (automatic IndexNow submission) scoped to 'this site', which is enough to separate it from get_indexnow_status and submit_indexnow. It stops short of explicitly naming those siblings, so an agent must infer the boundary rather than being told.

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 parenthetical '(on by default)' is the only decision support offered: it implies the agent only needs this tool when the feature has previously been switched off. There is no explicit when-to-use/when-not guidance and no mention of get_indexnow_status or submit_indexnow as alternatives, so 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.