perseus_health

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

Annotations declare readOnlyHint=true. Description adds 'Read-only; returns status enum and metric counts', consistent with annotations and provides extra context about return type. Minor gap: doesn't detail exact metric names.

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 with distinct value: purpose, usage guidance, and behavioral note. No redundancy; front-loaded with verb and resource.

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?

Covers purpose, usage, and behavioral traits adequately. However, the optional parameter lacks explanation beyond schema, and the return format (status enum, metric counts) is mentioned but no example provided. Adequate but not fully comprehensive.

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 for the only parameter 'args' is minimal ('Arguments for @health directive'). Description adds no extra meaning about what arguments are valid or how to use them. Despite 100% schema coverage, the description fails to enrich parameter understanding.

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 audits workspace context health, lists specific items it checks (stale skills, duplicate tasks, oversized output), and distinguishes from sibling perseus_get_health which covers deep heuristics.

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 before starting work to catch drift' and directs to perseus_get_health for Daedalus heuristics, providing clear when-to-use and when-not-to guidance.

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