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 behavioral constraint — 'Metadata/approved fields only; no secrets, contacts or original files' — clarifying the data-exposure boundary. It still says nothing about what the returned status contains or how pagination behaves.

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, front-loaded sentences with no filler beyond the slightly redundant 'through the existing application'. The data-scope caveat is correctly placed immediately after the core purpose.

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?

No output schema exists, so the description should explain the shape of a 'status' response, and it does not — it only bounds what is excluded. Combined with three undocumented pagination/filter parameters, an agent knows the intent but not the mechanics of calling or reading the result.

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% for all three parameters (limit, query, offset), and the description does not compensate at all — it never mentions pagination, the default page size, or what 'query' filters on. An agent cannot tell from either source whether this returns a single status object or a paginated list.

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+resource: reading the Gusto integration status. The vendor-specific scope distinguishes it from the many sibling get_*_integration_status tools, though the description never explicitly contrasts those alternatives.

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 the other integration-status siblings (Paychex, 7shifts, Toast, UKG, etc.) and no prerequisites or exclusions. The 'authorised... through the existing application' phrase hints at a connected-integration precondition but does not spell it out.

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