alcove_doctor

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

No annotations provided, so description must carry behavioral context. It only states 'check health' without disclosing read-only nature, side effects, or what 'health' means. Does not mention if it modifies state or requires special permissions.

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?

Extremely concise (5 words), but at the expense of usefulness. Overly terse; fails to provide critical information expected for a tool with no annotations and a single parameter.

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?

Despite having an output schema and one optional parameter, the description leaves major gaps: unknown output semantics, unclear behavior, and no parameter explanation. Does not cover basic actionable details.

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 coverage is 0% (the 'workspace' parameter has no description). The tool description does not explain the parameter's purpose or default behavior. This fails to add meaning beyond the schema.

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 a specific verb-resource action ('Check managed knowledge base health'), and although it does not explicitly distinguish from sibling tools like alcove_validate, it implies a health-check role. Not a tautology; adds meaning to the name 'doctor'.

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 (e.g., alcove_validate). No context on prerequisites, when to avoid, or typical scenarios. The single sentence provides no usage direction.

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