nim_status

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

No annotations exist, so the description carries the full burden. It usefully discloses the concrete 40 RPM quota and that the call surfaces telemetry and catalog data, which implies a side-effect-free read, but it never explicitly states that it performs no mutations or consumes no quota. No auth requirements, cost, or freshness/caching behavior is mentioned.

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 front-loaded sentence with no preamble or filler; every listed item corresponds to real returned content. Slightly list-dense, but it earns its length by enumerating the response sections the agent will get back.

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?

With no output schema and no annotations, the description compensates by enumerating the categories of information returned (quota status, slots, telemetry, model catalog, aliases). For a zero-parameter read tool, that is nearly sufficient; only the explicit read-only guarantee and quota-consumption behavior are missing.

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 and the baseline is 4. Schema coverage is 100% and the empty object is self-explanatory.

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?

Uses the specific verb 'Reports' with a concrete resource set: rate limiting status, available slots, telemetry, and model catalog/aliases. Every sibling tool (nim_query_model, nim_review_code, etc.) performs work, so an agent can immediately tell this one is the informational/state-introspection tool. No ambiguity about what calling it returns.

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 content ('40 RPM quota', 'available slots') strongly implies you'd call this to check remaining capacity before or during model invocations, but the description never says that. There is no explicit when-to-use statement, no prerequisite, and no reference to the sibling tools it would precede. Usage is inferable but not stated.

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