Google Ads Cache Status

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint. The description adds concrete behavioral details: never calls Google Ads and does not require credentials, plus lists exact return fields. This goes beyond annotations and provides confidence in the tool's behavior.

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: first lists return fields, second emphasizes read-only and no credentials. Every sentence is necessary and front-loaded. No 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?

Given the output schema exists to document return values, the description covers all necessary behavioral and usage context: purpose, read-only nature, no credentials, and no external calls. It is complete for a simple status-check 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?

The only parameter (response_format) is not mentioned in the description, resulting in 0% schema coverage. Although the schema is self-explanatory with enum and default, the description does not add any value for parameter semantics, which is required given low coverage.

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 returns SQLite GAQL-response cache status with specific details (enabled flag, path, entry count, oldest entry age, default TTL). It implicitly distinguishes from siblings by noting it is read-only and never calls Google Ads.

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 clear context: read-only and no credentials needed, so it can be used safely without side effects. However, it does not explicitly mention when not to use or list alternatives, leaving some inference to the agent.

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