9router providers

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

The annotation already establishes readOnlyHint=true. The description adds the behavioral disclosure 'no secrets', reassuring that the response contains no sensitive data. It does not describe further behavioral details such as response format or rate behavior, but for a zero-parameter read-only tool this is acceptable.

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 short and front-loaded, with no wasted words. 'Provider health' carries the core meaning, though 'no secrets' is somewhat cryptic and could be clearer as a separate safety note.

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 simple, parameterless, read-only tool with an output schema, the description provides sufficient context about what the tool returns. It is slightly thin on usage context and sibling differentiation, but the low complexity lowers the completeness burden.

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%, so the schema fully captures parameter semantics. The description adds no parameter detail, but none is needed.

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 identifies the resource as 'providers' and the subject as 'health', which is specific and distinguishes it from sibling tools like nine_models or nine_usage. It lacks an explicit verb such as 'list' or 'get', so it is clear but slightly elliptical.

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?

There is no guidance about when to use this tool over siblings like nine_status or nine_models. No alternative tools or selection criteria are mentioned, leaving the agent to infer placement from the name alone.

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