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

Annotations already declare readOnlyHint, idempotentHint, and openWorldHint=false, so the safety profile is covered. The description adds the non-obvious sequencing behavior — that this is the entry-point lookup that resolves 'my site' ambiguity — which annotations cannot express. It stops short of any format/pagination detail, but the payload shape is already enumerated.

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?

Two sentences, no filler, and the payload enumeration comes before the routing rule. Slightly dense, but every clause carries information — nothing restates the name or title.

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 lookup with no output schema, the description compensates by enumerating the returned fields (domain, name, plan, question count, integrations) and by explaining when to call it. Nothing an agent needs to invoke it correctly is missing.

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?

Zero parameters, so there is nothing for the description to disambiguate; baseline 4 applies. The description correctly implies the call is parameterless by framing the result as scoped to 'this connection'.

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?

States exactly what the tool returns — the connection's brand: domain, name, plan, tracked question count, and connected integrations — which is a specific resource with an enumerated payload. It is clearly distinguishable from the my_* siblings (my_questions, my_visibility, my_search_console), which each cover a narrower slice.

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?

Explicit routing instruction: 'Call this first whenever the user says my site, my website or my domain, rather than asking them which site they mean.' It states both the trigger phrase and the behavior to avoid, which is exactly what an agent needs for tool selection among many my_* tools.

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