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

The description adds useful behavior beyond the readOnly/idempotent annotations: it lists all sitemaps (no filtering), scopes results to a Search Console property, and discloses the output categories (status, indexing coverage, errors, warnings). It also exposes a required dependency on get_site_list for the correct site_url, which is important invocation context.

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 compact and front-loaded with the primary action, then the use cases, then the routing prerequisite. Each sentence earns its place and there is no redundant filler.

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 read-only list tool with two well-documented parameters and annotations, the description covers purpose, use case, output content, and the required preceding call. It does not detail pagination or a full return contract, but with no output schema and clear scope this is sufficiently complete for correct 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%, so the schema already fully documents both site_url and companyId. The description adds a mild semantic link by calling site_url a 'property' and telling users to get the correct value from get_site_list, but it does not add format details or clarify companyId beyond what the schema provides. This is the expected 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 names a specific verb and resource: 'List all sitemaps submitted to Google Search Console for a property.' It also states the output highlights (submission status, indexing coverage, errors, warnings), which separates it from generic list tools and nearby siblings like get_site_list or get_search_performance.

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 gives clear usage context: 'Use for technical SEO audits and crawl coverage analysis.' It also provides an explicit prerequisite with routing guidance: 'Call get_site_list first to get the correct site_url.' It lacks explicit when-not-to-use guidance or alternatives, but the routing and use-case framing are strong.

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