Google Search Console MCP

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 documents input format constraints but fails to disclose operational traits such as whether the operation is idempotent, what happens if the site already exists, verification requirements, or success/failure responses.

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 front-loaded with the primary action and reasonably sized at two sentences. However, the 'Args:' block format is slightly awkward for MCP contexts and could be more integrated, though it remains readable.

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 single-parameter tool with no output schema, the description adequately covers the parameter's semantics. However, it lacks information about return values, error conditions, or side effects that would be expected for a property creation 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?

Given 0% schema description coverage, the description effectively compensates by documenting the site_url parameter in the Args block, providing critical format examples (https://, sc-domain:) and constraints (exact match) that the schema lacks.

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 'Add a site to your Search Console properties', providing a specific verb (Add) and resource (site). It effectively distinguishes from the sibling 'delete_site' tool, though it could explicitly mention 'Google' Search Console for absolute clarity.

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 detailed format requirements for the site_url parameter (exact match examples, domain property syntax), but offers no guidance on when to use this tool versus alternatives like 'list_properties' or 'delete_site', nor prerequisites for adding sites.

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