get_site_details

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

No annotations are provided, so the description must convey behavior. It only says 'Get detailed information' and provides parameter guidance. It does not mention potential errors, authentication, read-only nature explicitly, or any side effects, which is a significant gap.

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 concise and well-structured, with a one-sentence purpose followed by a focused Args section. Both parts are necessary and add value without redundancy.

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 is simple (1 required param) and has an output schema, but the description lacks behavioral details and explicit usage alternatives. While the parameter guidance is thorough, the overall context is somewhat minimal given no annotations.

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 provides no description for site_url (0% coverage). The description compensates excellently with exact format, two examples, and an explanation of domain vs URL-prefix properties, making it clear what to pass.

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 it retrieves detailed information about a specific Search Console property, with a specific verb and resource. It distinguishes from siblings like list_properties by emphasizing 'specific' property, though it doesn't enumerate the details.

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 instructs that site_url should come from list_properties, establishing a prerequisite. It also explains domain property behavior and filtering for subdomains. However, it doesn't explicitly name alternative tools or state when not to use this one.

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