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

With no annotations provided, the description carries the full burden of behavioral disclosure. It does disclose the read-only nature and that submission is impossible, which is useful. But it does not mention what status values may appear, whether an empty list is returned, or any error behavior, leaving a notable gap for a tool with no output schema.

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 two short sentences with no filler. The core purpose is front-loaded, and the read-only caveat is useful. The phrase 'submitting is not possible with read access' is slightly redundant after 'Read-only', but the overall structure is tight.

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 list operation, the description combined with the schema provides enough for an agent to call the tool correctly. It could optionally clarify the status vocabulary or return format, but the absence is not a serious gap given the tool's simplicity.

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%, and the site parameter is already documented with exact formats in the schema. The description adds no additional parameter meaning, which is acceptable because the schema does the work; 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 identifies the resource (sitemaps submitted for a property) and the kind of information returned (their status), which distinguishes it from sibling tools like list_sites. It lacks an explicit imperative verb like 'List', relying on the tool name to supply the action, so it is clear but not maximally explicit.

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 provides a clear boundary: this is read-only and cannot be used to submit sitemaps. However, it does not explicitly state when to prefer this over alternatives or mention any related constraints such as requiring the property to already exist. Usage context is implied rather than spelled out.

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