integration_status

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

No annotations are provided, so the description carries the burden. It discloses the required scope 'integrations:status:read' and the governance/receipt behavior ('governed by Arbiter constitutional policy and sealed with a ProofLink cryptographic receipt'). It does not address potential error states or network effects, but for a read-only health check this is adequate.

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 description is two sentences: first states the function and response, second states requirements. No filler or repetition, front-loaded with 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?

The tool is simple (zero params) and the description lists all affected services, the response format (ok:true/false and metadata), and access requirements. Since there is no output schema, a slightly more detailed return contract would help, but the current coverage is sufficient for an agent to invoke this tool correctly.

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 input schema has zero parameters, so there is no parameter documentation burden. The description doesn't need to explain parameters, and it doesn't introduce any ambiguity about 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 uses a specific verb phrase 'Parallel health check' and enumerates the exact integrations (Langfuse, RAGflow, Shuffle, Tactical RMM, MeshCentral, Probo compliance). It clearly indicates it aggregates status across all services, distinguishing it from individual sibling health-check 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?

It presents a clear context: a holistic overview of all wired integrations. However, it does not explicitly state when to prefer this over individual health checks or provide explicit alternative tool references, so it misses the explicit 'when-not' guidance.

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