Hub Health

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

With no annotations, the description carries the full burden; 'Return' implies a read-only check and the future-provider caveat hints at a side-effect-free scope, but auth requirements, cost, and behavior are unstated. The presence of an output schema relieves it of explaining return values, which keeps this at an adequate 3.

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 compact sentence with the action front-loaded and the constraint immediately after. Nothing is wasted, though the 'future providers' phrasing is cryptic enough to require interpretation.

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 read with an output schema, the definition covers what the tool does and one important scope limit. Only the meaning of 'future providers' and the relationship to hub_capabilities are left open.

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 takes zero parameters, so there is nothing for the description to disambiguate; baseline 4 applies.

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 verb ('Return') and resource ('local server readiness'), so the agent knows this is a health/status check rather than a capability listing. The scope caveat ('local') helps separate it from hub_capabilities, though the sibling is never named and 'readiness' is slightly abstract.

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?

Provides one explicit exclusion ('do not probe future providers'), which is real when-not guidance. However, it never says when to prefer this over hub_capabilities or what 'future providers' means, so the routing guidance is only implied.

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