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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds a genuine data-boundary disclosure beyond annotations: 'Metadata/approved fields only; no secrets, contacts or original files,' which tells the agent what it will not get back. It still omits response shape and pagination 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?

Two short sentences with the purpose front-loaded and the data-scope caveat second. No filler, though the clause 'through the existing application' is vague enough to be near-waste.

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?

Purpose and data boundaries are adequately covered for a read-only status tool, but with no output schema and 0% parameter documentation, the description should say what the status payload contains and how the list is paginated. Minimum viable rather than complete.

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?

Schema description coverage is 0% – none of the three parameters (limit, query, offset) carry any documentation. The description does not mention them at all, so there is no indication of what 'query' searches over or how limit/offset interact. Only the conventional parameter names salvage minimal interpretability.

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 a specific verb and resource ('Read authorised googlesheets integration status') and scopes it to the existing application, which is enough to separate it from the other integration-status siblings (7shifts, adp, gusto, etc.) that are already distinguished by name. It stops short of explicitly naming when this differs from the broader list_* metadata tools.

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?

No statement of when to call this versus alternatives, no prerequisites, and no exclusions. The phrase 'through the existing application' is ambiguous rather than directive, so the agent must infer usage entirely from the tool name.

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