healthcheck

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

Discloses the HTTP GET call and return value, but does not mention authorization or safety implications. However, it is a read-only healthcheck with no side effects.

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?

Concise two-sentence description with bilingual support, front-loading the English purpose and providing all necessary information without redundancy.

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 return format with example, parameter usage, and endpoint details. The presence of an output schema complements the description, making it fully informative.

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?

The description fully explains the optional 'instance' parameter, including its purpose and default behavior, adding value beyond the bare schema which lacks descriptions.

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 tool checks if an Alefba instance is up and ready, specifies the HTTP endpoint and return format, and distinguishes itself from sibling document management tools.

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?

Describes the optional 'instance' parameter and default behavior, but lacks explicit guidance on when not to use or alternatives, though the context of siblings makes this clear.

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