healthcheck

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

Discloses the endpoint called, auth requirements (none), response format (reachable, pairs_count? or error), and default instance behavior. No hidden side effects mentioned, but as a health check, read-only is clear.

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?

Well-structured with clear purpose, endpoint, and parameter details. The Persian section is slightly redundant but not overly verbose. Front-loads key info.

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's simplicity (one optional param, output schema available), the description is complete enough for an agent to use correctly. Error handling is briefly noted.

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 explains the 'instance' parameter beyond the schema, including default and token requirement. Since schema coverage is 0%, this adds necessary 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 tool checks Ramzinex reachability via a lightweight public endpoint, specifying the exact API path and that no auth is needed. It distinguishes itself from siblings focused on trading or auth.

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?

Implies usage for connectivity checks without auth, but does not explicitly contrast with sibling tools or advise when to prefer this over others. No exclusion criteria given.

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