flowapi_health_check

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

No annotations exist, so the description carries full responsibility for behavioral disclosure. It only states the purpose and does not disclose any side effects, required permissions, response format, or error behaviors. For a health check tool, details like whether it returns a boolean or a detailed status object are missing, leaving the agent with insufficient behavioral 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?

The description is extremely concise: two sentences totaling 12 words. It is front-loaded with the primary purpose. Every word earns its place; there is no redundancy or filler.

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 simplicity (no parameters, no output schema, no annotations), the description is still incomplete. It does not explain what the response contains (e.g., health status, connectivity details) or how the agent should interpret the result. A health check tool typically benefits from mentioning return format or success criteria, which are absent here.

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 tool has zero parameters and schema coverage is 100% trivially. Per guidelines, 0 parameters sets a baseline of 4. The description does not add parameter-specific meaning, but none is needed since no inputs are required. No further elaboration on parameters is necessary.

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's purpose: 'Check FlowAPI system health and connectivity. Verifies system is operational.' The verb 'check' and resource 'FlowAPI system health' are specific. It distinguishes from siblings like 'flowapi_system_info' by focusing on health/connectivity rather than general system info.

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 is provided on when to use this tool versus alternatives (e.g., flowapi_system_info). There is no mention of prerequisite conditions, when not to use it, or typical use cases beyond the basic description. The agent must infer usage solely from the name and purpose.

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