Unified setup diagnose

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

States 'Read-only', matching annotations. Discloses that the tool runs checks but is non-destructive and idempotent. Details what each mode checks and the return format, giving full behavioral context beyond annotations.

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, front-loaded with purpose and return. Every sentence adds essential information without redundancy. Highly efficient.

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 output schema exists, the description still covers all behavioral aspects: modes, checks included, return structure, and safe nature. No gaps for a read-only diagnosis tool.

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?

With 100% schema coverage, the description adds significant value by explaining the mode enum values (full, ingest, dispatch) and their meanings, noting that mode defaults to full, and clarifying project_id usage for dispatch checks.

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 clearly uses the verb 'diagnose' with 'Mushi setup health' and states the goal to return the single best next action. It distinguishes itself from siblings by claiming to be the unified entry point.

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 'the one setup-diagnosis entry point — use this instead of separate connection/ingest checks', providing clear guidance on when to use and when not to use alternatives. Also explains the three modes.

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