get_site_details

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

No annotations are provided, so the description carries full burden. It notes that domain properties cover all subdomains and suggests filtering by page, which is useful behavioral context. However, it doesn't mention read-only nature, authentication, or potential errors, leaving gaps.

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 well-structured sentences plus an args block, with no waste. It front-loads the purpose and gives concise, focused parameter guidance.

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 single-parameter tool with an output schema (not shown), the description adequately covers parameter semantics and usage. Missing details about errors or auth are minor for a getter, and return format is covered by the output schema.

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 has a bare string parameter with no description, and the description fully compensates with examples, source from list_properties, and domain property semantics. This significantly exceeds schema information.

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 it retrieves detailed information about a specific Search Console property, clearly distinguishing from list_properties by focusing on one property. However, 'detailed information' is somewhat generic, so it's not a 5.

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 specifies that site_url must be the exact GSC property URL from list_properties, providing a clear workflow. It also explains how to handle domain properties to analyze subdomains. It does not explicitly mention alternative tools or when not to use this tool, but the guidance is clear.

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