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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so the safety profile is covered. The description adds a genuine data-scope constraint ('metadata/approved fields only; no secrets, contacts or original files'), which is useful behavioural context, but it says nothing about pagination behaviour or what a 'status' response contains.

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 subject front-loaded and no filler. The second sentence earns its place by narrowing the data scope, though the phrase 'through the existing application' is vague filler.

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?

With no output schema, undocumented pagination parameters, and no statement of what fields a 'status' result includes, the description leaves too much for the agent to infer for a tool that appears to return a paginated collection.

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% and the description mentions none of the three parameters. It is unclear whether 'query' searches integration metadata or filters records, and the presence of limit/offset implies a paginated list rather than a single status object, which the description never reconciles.

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 7shifts integration status'), and the provider name alone distinguishes it from the many sibling integration-status tools (gusto, adp, toast, etc.). It doesn't explicitly route against siblings, but an agent can identify the target without ambiguity.

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 when-to-use, when-not-to-use, or prerequisite guidance is given. 'Through the existing application' is vague and does not tell the agent whether this requires a pre-existing 7shifts connection or what to do if none exists.

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