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

Annotations already establish that this is read-only, idempotent, non-destructive, and closed-world. The description adds meaningful scope context: only metadata/approved fields are exposed, and secrets, contacts, and original files are excluded. It stops short of explaining pagination or response shape.

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, purpose front-loaded, with no wasted wording. The second sentence efficiently adds the important data-scope restriction. The phrase 'through the existing application' is slightly vague but does not undermine concision.

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 simple read-status tool, annotations and the data-scope note cover safety and privacy well. However, with no output schema and no parameter descriptions, the definition does not explain what status data is returned, how to paginate, or what the query parameter matches.

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 schema has three parameters (limit, query, offset) with 0% description coverage, and the prose does not explain any of them. It gives no meaning for what query filters on, how pagination works, or what limit/offset control, leaving the parameters effectively undocumented.

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: reading Toast integration status. The product name distinguishes it from the many sibling integration-status tools, but it does not explicitly contrast with alternatives or clarify whether this covers configuration, health, or connection state.

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 status-read tool but gives no when-to-use conditions, prerequisites, or alternatives. It does not tell the agent when to choose this over other integration-status tools or when status info is insufficient.

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