Check which Google data the project has

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds valuable behavioral context: a project with nothing bound answers with zeros and empty lists, which reads exactly like a site nobody visits. This is a non-obvious behavioral trait that helps the agent interpret results correctly. It doesn't describe the exact return format, but with no output schema and zero parameters, the description carries the burden well.

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 sentences, front-loaded with the core purpose, and every sentence earns its place. The first sentence states what it does; the second explains when to use it and the critical interpretation pitfall. No wasted words.

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 zero-parameter, read-only tool with no output schema, the description is complete. It explains what the tool checks, when to call it, and how to interpret the zero/empty-list case. The agent has everything it needs to invoke and interpret the tool correctly.

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 tool has zero parameters, so the schema provides no parameter semantics. The description compensates by explaining what the tool reports (binding status and last sync for two integrations). A baseline of 4 is appropriate for a zero-parameter tool where the description clarifies the tool's output semantics.

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 tool's purpose: checking whether Search Console and Google Analytics are bound to the active project and how their last sync went. It uses specific verbs and resources, and it distinguishes itself from siblings like get_search_performance and get_ai_traffic by focusing on integration binding status rather than metrics.

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 gives explicit when-to-use guidance: call this when a Google figure looks wrong or empty, or before promising a report built on one. It also explains the critical pitfall of confusing an unbound integration with a site that has no traffic, and instructs the agent to call this before reporting a zero as a finding. This is strong usage guidance.

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