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

With no annotations provided, the description carries the burden of behavioral disclosure. 'Check' clearly implies a read-only, non-destructive operation, and naming the specific status scope (configuration and connection) adds useful behavioral context. It does not detail output shape or failure behavior, but for a zero-parameter status tool this is adequate.

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?

The description is a single, front-loaded sentence with no filler. Every word adds meaning, naming the action, the resource, and the specific providers covered.

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 tool with no parameters and no output schema, the description adequately covers what the tool does and which providers it inspects. It could mention expected return values or that it is non-mutating, but the scope and purpose are clear enough for an agent to select and invoke it 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 tool has zero parameters, so the description has no parameter semantics to add. Per the baseline for zero-parameter tools, this scores a 4; the description is not penalized for omitting parameter details that do not exist.

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 has a clear verb ('Check') and a specific resource ('configuration and connection status of all integrated search engine providers'), and it enumerates the providers. This clearly distinguishes it from siblings like list_sites or search_analytics, which operate on site data rather than provider connection health.

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 tool is for diagnosing provider integration health, which is a distinct use case from the sibling tools. However, it does not explicitly state when to use this tool versus alternatives, nor does it mention any exclusions or prerequisites.

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

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

No annotations exist, so the description carries the safety disclosure burden. 'Retrieve' implies a non-mutating read operation, which is useful, but the description does not disclose authentication requirements, rate limits, or what counts as an error metric. It is not misleading, but it is thin on behavioral detail.

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?

The description is a single sentence with no filler, repetition, or structural clutter. It front-loads the verb and object, making the tool's core purpose immediately scannable.

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?

There is no output schema, and the description does not compensate by explaining what 'deep indexing and error metrics' concretely include or how the response is shaped. Combined with absent annotations and no usage/alternative hints, the picture is incomplete for an agent that must interpret the returned metrics.

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%, so all three parameters already carry semantic descriptions in the schema. The tool description adds no additional parameter-level meaning beyond restating that the feed is a sitemap, so it does not go beyond the schema baseline.

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 clear action ('Retrieve') on a specific resource ('a specific sitemap feed') and names the output domain ('deep indexing and error metrics'). It can be distinguished from siblings like list_sitemaps by the focus on a single feed, but it does not explicitly name alternatives or state exclusions, so it stops short of full differentiation.

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?

No explicit when-to-use or when-not-to-use guidance is provided. The phrase 'specific sitemap feed' hints at the intended scope, but the description never directs the agent to list_sitemaps for enumeration, inspect_url for individual URLs, or otherwise states trade-offs between sibling tools.

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

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

With no annotations, the description carries the responsibility for behavioral disclosure. It correctly implies a read-only inspection operation and clarifies results are live, but it omits operational details such as verification requirements, engine-specific limitations, rate limits, and the exact response shape.

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?

A single, front-loaded sentence communicates the action, platform scope, and intended checks without filler or repetition. The enumerated list is compact and scannable.

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?

Given the full parameter schema and the description's explicit list of output categories, an agent has enough context to select and invoke the tool correctly. The absence of an output schema is partially compensated by naming the checks, though a note on return format or required site verification would make it fully complete.

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%, so all four parameters are already documented in the schema. The description adds no new meaning to parameters like siteUrl or languageCode; it merely frames the high-level action. Baseline 3 applies since the schema does the heavy lifting.

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 ('Inspect') against a specific resource ('a URL'), names both target platforms, and enumerates concrete checks (indexing status, crawl info, canonical URLs, mobile usability, rich results). It is immediately distinguishable from siblings like search_analytics or list_sitemaps.

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 'to check ...' clause defines clear use cases: when an agent needs live indexing, crawl, canonical, mobile, or schema-validation data for a single URL. It does not explicitly state when not to use it or name alternatives, but the purpose sentence supplies enough context against sibling names.

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

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

Because no annotations are provided, the description itself must carry behavioral disclosure. Its output-field list does add useful detail, and 'List' implies a read-only operation, but it does not state prerequisites (verified siteUrl), inclusion rules, or any caveats about error counts/status. This is adequate but not comprehensive.

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 contains a clear action verb, resource, and a compact list of returned fields; no filler or repetition. It is appropriately front-loaded and easy to scan.

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 2-parameter read-only listing, the description conveys the core purpose and output fields, but with no output schema and no annotations it leaves routing and prerequisites implicit. The missing guidance around sibling tools and exact response shape keeps it from being fully complete.

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 100%; the schema already explains siteUrl as the verified Search Console site URL and documents engine as an enum with default 'google'. The description adds no semantic value beyond referencing submitted sitemaps, 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 opens with a specific verb and resource ('List all submitted sitemaps') and enumerates the exact fields returned (status, last download date, error counts, indexed URL counts), making its function unambiguous. The plural 'all' naturally contrasts with sibling get_sitemap, which implies a single-sitemap retrieval.

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?

No sentence tells an agent when to choose this tool over siblings such as get_sitemap or engine_status. The only use condition is implicit in the verb 'List'; there are no exclusions or alternative routing. This leaves selection to inference.

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

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

With no annotations provided, the description carries the behavioral burden. 'List' indicates a read-only, non-destructive operation, but the description does not mention authentication requirements, response format, pagination, or any side-effect guarantees. It is adequate for a simple list tool but not richly transparent.

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?

A single sentence that front-loads the core action and resource, then adds the permission-level output detail. Every word earns its place; no redundant filler or repetition of schema content.

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-parameter, no-output-schema list tool, the description covers the essential purpose and result content. It does not describe the exact return structure or pagination, but the tool is simple enough that this omission is a minor gap rather than a blocker.

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 'engine' is fully described in the schema with an enum and default, so schema coverage is 100%. The description adds no additional parameter-specific meaning beyond naming the two platforms, which the enum already conveys. Baseline 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?

States a specific verb ('List') and resource ('verified sites/properties') across two named platforms, and includes the permission-level detail. This clearly distinguishes it from sibling tools like list_sitemaps or inspect_url.

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 conveys clear context: use this tool to get all verified sites across Google Search Console and Bing Webmaster Tools. It does not explicitly name alternatives or exclusion conditions, but the scope is unambiguous enough for an agent to select it appropriately.

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

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

No annotations are provided, so the description carries the full behavioral burden. The verb 'Query' conveys read-only intent, which is the key safety-relevant trait. However, it does not disclose provider-specific differences between GSC and Bing APIs, rate limits, or the aggregated/grouped nature of the result rows. Adequate but thin given zero annotation coverage.

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?

A single 23-word sentence that is front-loaded with the action and resource, names the returned metrics, and identifies both providers. There is no filler, and every phrase 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?

The tool is moderately complex — 13 parameters, two providers, no output schema, no annotations. The schema fully documents parameters and the description names the return metrics, but the description omits provider-specific caveats, result aggregation semantics, and usage boundaries. Sufficient for basic invocation with the three required parameters, but incomplete for nuanced calls.

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% with every parameter already documented (enums, defaults, date formats, filter syntax), so the baseline is 3. The description adds marginal value by naming the computed metrics, which conceptually maps to what the tool returns, but it contributes nothing about parameter syntax or constraints beyond the schema.

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 ('Query'), a specific resource ('search performance and analytics data'), enumerates the returned metrics (clicks, impressions, CTR, average position), and names both supported providers (Google Search Console, Bing Webmaster Tools). It is immediately distinguishable from siblings like inspect_url (URL-level data) or list_sitemaps (sitemap management) without needing to inspect the schema.

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 use case is implied by the resource it queries — aggregate search performance metrics across two engines — and the sibling names make the contrast obvious. However, the description never explicitly states when to use this tool over an alternative, nor does it mention exclusions or prerequisites, leaving the agent to infer routing from sibling names alone.

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

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

No annotations are provided, so the description must carry the burden of behavioral disclosure. It only states the core action and does not mention authentication key requirements, idempotency, rate limits, or expected response/error behavior, leaving a significant gap for a write operation.

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?

A single, front-loaded sentence with no filler. The verb and target are immediate, and every word contributes to the meaning.

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?

With four parameters, no annotations, and no output schema, the description is minimal. It does not explain what happens after submission or any constraints like URL limits. However, the schema fully documents parameters, so an agent can still construct a valid request.

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%, so the schema already documents all four parameters. The description adds no extra meaning about key, host, urls, or keyLocation, so the baseline of 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 uses a specific verb ('notify') and names the exact resources (Bing, Yandex, Seznam, and other IndexNow search engines) and the event types (added, updated, or deleted URLs). This clearly distinguishes it from read-oriented sibling tools like inspect_url or list_sitemaps.

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 a clear use case: after content changes, notify IndexNow engines. However, it does not explicitly state when not to use this tool or mention alternatives like submitting via sitemaps, though the context is clear enough for an agent to infer when it applies.

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