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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint, so the safety profile is covered. The description adds a genuine behavioral fact — the read works without credentials — but the closing sentence about MCP approval requirements and business workflow approvals reads as generic platform boilerplate rather than describing how this specific tool behaves or what it returns.

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 purpose and the no-credentials caveat are front-loaded in the first two sentences, which is good structure. The third sentence about approval configuration is tangential and dilutes focus, though the overall length remains tight.

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?

An output schema exists, so the description needn't explain return shape, and annotations cover the safety profile; the remaining job — telling the agent what the call does and its credential caveat — is done. Only the missing sibling routing keeps it from a 5.

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 tool takes zero parameters, so per the baseline there is nothing for the description to clarify and no schema coverage gap to compensate for. A 4 is appropriate for a no-arg tool whose description is not required to document inputs.

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 leads with a specific verb+resource: "Read credentialcamp integration status," which is unambiguous and lets an agent distinguish it from siblings like get_incidentvault_integration_status or get_policytrak_integration_status by the named integration alone. It does not explicitly contrast itself with those siblings or say what the status distinguishes (connected vs. not), so it falls just short of a 5.

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?

It offers one useful routing hint — credential configuration happens through the secure settings screen, not this tool — which effectively tells the agent when this tool is insufficient. However, it never addresses the parallel integration-status tools or says when an agent should call this versus the linked-location creation tools for the same integration, leaving the primary selection decision implied.

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