get_site_details

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

No annotations are provided, so the description carries the burden. 'Get' implies a read-only operation, and the domain-property guidance adds useful behavior context, but it does not disclose authentication requirements, potential errors, or side-effect guarantees.

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: a clear lead sentence immediately followed by focused parameter guidance. There is no filler or repetition of schema information.

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 only one parameter, an output schema, and no nested objects, the description covers the essential invocation details. It could be slightly more complete with explicit when-to-use guidance, but the provided context is sufficient for a straightforward getter tool.

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 0%, but the description fully compensates for the single parameter by explaining the exact URL format, giving examples, and clarifying how domain properties behave. This is exactly the kind of guidance an agent needs to supply a correct site_url.

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 clearly states the operation: 'Get detailed information about a specific Search Console property.' It identifies the resource and uses a specific verb, though it does not explicitly differentiate itself from sibling tools like get_capabilities or get_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?

It provides clear context by instructing that site_url must come from list_properties and explains how to handle domain properties ('use the domain property as site_url and filter by page'). However, it does not explicitly state when to prefer this tool over alternatives.

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