doctor

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

The description explicitly says 'read-only', which informs agents it is non-destructive. However, it does not disclose performance impacts, authentication needs, or error handling. With no annotations, the description carries the burden and partially meets it.

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?

Single sentence, no redundancy, front-loaded with key information. Every part adds value.

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 the main checks, but lacks details on output format or what 'report baseline readiness' entails. Given simple parameters and no output schema, it is adequate but could be more precise.

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 coverage is 100%, and description does not add meaning beyond schema for the two parameters. The default for backup_max_age_hours is noted in schema, but no extra usage context.

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 states the verb 'run' and resource 'diagnosis', listing specific areas (resource pressure, stopped containers, etc.), and differentiates from sibling tools like 'system_status' or 'docker_stats' by being a comprehensive health check.

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 explicit guidance on when to use this tool versus alternatives like 'alerts' or 'system_status'. The description only states what it checks, not when or when not to use it.

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