elite_doctor

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

No annotations provided, so description must communicate behavioral traits. It only mentions 'run a health check', implying a read operation but not explicitly stating safety, auth needs, or potential side effects. Missing important context.

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?

Very concise, no wasted words. The structure is clear: action followed by parameters. Could be improved by front-loading more context, but it is efficiently written.

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 performs a health check and has an output schema (not shown), the description does not explain return values or output structure. No preconditions are mentioned, and the single parameter is only partially explained.

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 description coverage, the description adds value by listing the two output formats ('markdown or json') for the sole parameter. However, it does not explain what each format returns, leaving some ambiguity.

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 it runs a release-readiness health check for the MCP server, providing a specific verb and resource. However, it does not differentiate from sibling tools like 'elite_doctor_json'.

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 versus alternatives among its many siblings. Only states the action, not usage context.

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