Get Indexing Notification Status

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

Annotations already define the operation as read-only (readOnlyHint=true) and non-destructive (destructiveHint=false). The description adds a little context by stating what the tool returns (most recent update and removal notifications), but does not disclose other behaviors like empty states, response format, or potential errors. With annotations covering safety, this is adequate but not rich.

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 sentences with no fluff. The primary action is front-loaded, and the follow-up sentence clarifies the output scope. Every word 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?

For a simple one-parameter read-only tool with no output schema, the description is complete enough for an agent to select and invoke it correctly. It states what is checked, what the result contains, and the required input is clear from the schema. Nothing essential 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?

The schema provides 100% coverage for the sole parameter, with a description ('The URL to check notification status for'). The tool description simply repeats 'for a URL' without adding value beyond the schema, so the baseline of 3 is 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?

The description uses a specific verb ('Check') and a clear resource ('status of Indexing API notifications for a URL'), and specifies that it shows the most recent update and removal notifications. This clearly differentiates it from siblings like notify_url_update because it's about checking status, not sending notifications.

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 the usage scenario: after notifications have been sent, an agent can check their status. However, it does not explicitly state when to prefer this tool over alternatives, nor does it mention any exclusions or prerequisite actions. This leaves the guidance at an implied level.

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