hub_health_check

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It states that it returns connection status and capabilities, but does not disclose whether the operation is read-only, whether it makes external API calls, or any side effects, rate limits, or auth requirements. This is a significant gap for a tool that presumably accesses external marketing platforms.

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 two sentences, highly concise, and front-loaded with the primary action. Every word adds value, with no bloat or tautology. It efficiently states the scope ('ALL connected') and the return type ('connection status and capabilities').

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 tool with no output schema, the description is reasonably complete: it states the resource, scope, and what is returned. However, it lacks specifics on the format of the return value (e.g., how status is represented) and does not mention any potential failure modes or latency. Given the simplicity, this is acceptable, but a tad more detail on the return structure would improve it.

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 0 parameters, so schema_description_coverage is trivially high (100%). Per the rubric, 0-parameter tools receive a baseline of 4. The description does not need to explain parameters, and it doesn't—there is no 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?

The description clearly states the tool's function: check health status of ALL connected marketing platforms. The verb 'check' and the resource 'marketing platforms' are specific, and it distinguishes itself from sibling tools like hub_list_platforms (which lists platforms) and hub_get_dashboard (which gets a dashboard) by focusing on health status and capabilities.

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 provides no guidance on when to use this tool versus alternatives. It does not mention any conditions, exclusions, or related tools. While the purpose is implied (health monitoring), there is no explicit routing or comparison to sibling tools, leaving the agent to infer usage context.

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