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

No annotations are provided, so the description carries full burden for behavioral disclosure. It reveals that the tool is public and that other operations require OAuth, but it does not describe what 'health' or 'catalogue' include, nor mention any rate limits, response format, or side effects. The transparency is weak.

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 a single sentence with no filler. It front-loads the key information and the second clause adds useful authentication context. Every word earns its place.

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 (zero parameters, no output schema, no siblings), so the description does not need extensive detail. However, it is vague about the exact contents of the 'health' and 'catalogue' summary, which could leave an agent uncertain about what to expect. It is minimally adequate but not rich.

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 parameter semantics are trivially satisfied. Per the baseline rule, a zero-parameter tool earns a 4 because the description does not need to compensate for undocumented parameters.

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 provides a 'Public health and catalogue summary' for OrbiAds MCP, which is specific enough for an agent to understand its purpose. It lacks a verb but the noun phrase is unambiguous. No siblings exist to differentiate, but the scope is clear.

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 implies this is a read-only, public summary tool that does not require OAuth, and explicitly notes that Google Ad Manager operations still require OAuth. This provides some contextual guidance for when to use this tool, but does not explicitly state when to prefer it over alternatives.

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