cloud_diagnose

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

Discloses full behavior: local+cloud operation, latency (~2-3s), return structure, auth requirement, endpoint override via env var. Without annotations, this is thorough.

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?

Three sentences, each serving a distinct purpose: what it does, return format, usage guidance. Front-loaded with key information.

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?

Given no output schema, description explains return structure in detail. Also covers endpoint, latency, auth. Complete for a tool of this complexity.

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 covers the only parameter (sharedSecret) with description; description adds endpoint and env var context but doesn't significantly enhance parameter semantics. Baseline 3 for 100% schema coverage, and extra context is minor.

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?

Clearly states the tool runs local diagnostics and relays to cloud for remediation, distinguishing it from sibling 'run_diagnostics'. Specific verb 'run' and resource 'local diagnostics + cloud-relay' provide clarity.

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?

Explicitly says 'Use this when local run_diagnostics surfaces warnings/errors and you want expert-level fix guidance', providing clear context. Does not explicitly list when not to use, but the condition is well-defined.

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