intuit_health_check

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

Description mentions routing through domain-agent dispatcher under JWT, tenant, and company scope, which discloses scope behavior. However, it does not state whether the action is read-only or has side effects, despite the health check name suggesting a safe operation. Without annotations, more disclosure about effects would be helpful.

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?

Description is short (4 sentences) and front-loaded with the purpose. Uses a structured Args list. No unnecessary fluff, though it could be slightly more concise.

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 the tool has an output schema (not shown), return values are covered elsewhere. However, the description does not explain the health check's purpose or how to effectively use the inputs. For a simple tool, it is minimally complete but lacks depth to fully guide an agent.

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 0% schema coverage, the description compensates by explaining 'message: Free-text objective' and 'inputs: Optional JSON string'. This adds meaning beyond the schema but remains vague – does not clarify how these inputs influence the health check or what valid formats are.

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?

Description clearly states 'Run the intuit domain agent action health_check' – a specific verb and resource. The name 'health_check' implies a health check operation, but the description does not elaborate on what the health check achieves, leaving some ambiguity.

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?

No guidance on when to use this tool vs alternatives like other intuit_* tools. The description lacks any context about typical scenarios or prerequisites.

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