get_site_details

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

This is a read-only 'Get' operation, which is implied but not explicitly stated. The description adds valuable context that 'Domain properties cover all subdomains' and advises using the domain property with page filtering, but does not disclose potential side effects, auth requirements, or rate limits. Since no annotations are provided, the description carries the full burden, and this is only partially met.

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 brief and front-loaded with the purpose, followed by a dedicated Args section. It avoids unnecessary detail and earns every sentence, making it efficient and well-structured.

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 has a single parameter and an output schema, so the description does not need to explain return values. It includes the prerequisite of using list_properties and gives practical advice for domain properties, making it adequately complete for a simple read tool. However, it could be slightly more explicit about the type of information returned and any prerequisites beyond authentication.

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 input schema only defines site_url as a string with no description (0% schema coverage). The description compensates fully by specifying the format, providing examples ('https://example.com/' or 'sc-domain:example.com'), and explaining domain property semantics, which adds significant meaning 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 clearly states 'Get detailed information about a specific Search Console property,' which uses a specific verb and resource. It implicitly distinguishes from sibling tools like list_properties (which lists properties) and get_search_analytics (which fetches performance data).

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 context by indicating the site_url should come 'from list_properties' and explains domain property behavior. However, it does not explicitly state when to prefer this tool over alternatives or when not to use it, such as for analytics or sitemap data.

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