Super Productivity: health check

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It discloses that the call is unauthenticated, which is a meaningful trait, but it does not state what the response looks like (e.g., status code or boolean) or confirm that it has no side effects. For a health check this is a moderate disclosure.

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?

A single sentence that front-loads the verb and resource, with no filler or redundancy. Every word contributes meaning, including the unauthenticated qualifier.

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?

For a zero-parameter health check, the description is largely sufficient: the agent knows what it does and that no authentication is required. The only missing context is what the tool returns (e.g., an HTTP status or response body), which would help the agent interpret the result, but the overall complexity is low.

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 input schema has zero parameters, so there is nothing to document. The 0-parameter baseline applies, and the description does not introduce any parameter-related 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?

States a specific action ('checks whether... reachable') against a named resource (the Super Productivity Local REST API) and qualifies it as unauthenticated. This distinguishes it from sibling CRUD tools like sp_task_get and sp_tasks_list, which operate on specific resources rather than the API's availability.

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?

The description implies the tool is used to verify API connectivity before other operations, but it does not explicitly state when to prefer it over alternatives or mention any exclusions. With siblings like sp_status present, a brief note about when to use this vs. other status-type tools would make it clearer.

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