Read local inference status

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

Annotations already declare readOnlyHint=true, openWorldHint=false and idempotentHint=true, so the safety baseline is covered. The description adds genuinely new behavioral context beyond that: no model is started, no network call is issued, and no host paths or secrets are exposed — the kind of disclosure an agent needs before calling a status probe in a sensitive environment.

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?

Two tight sentences with zero filler. The content enumeration comes first and the safety/no-side-effect guarantees second, which is the correct front-loading for an agent deciding whether to call it.

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 parameters, a full output schema covering the returned fields, and annotations covering the safety profile, the description needs only to add what structured data cannot express — and it does exactly that by stating the absence of model starts, network calls, and secret/path exposure.

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 per the rubric the baseline is 4. The description appropriately adds no parameter guidance because there is nothing to parameterize, and it instead spends its words on scope and safety.

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 gives a specific verb (read) plus a resource (local inference status) and enumerates exactly what the status covers: enabled state, readiness, capabilities, job counts and owner hard limits. It is clear what the tool does, but it never differentiates itself from related siblings such as local_generation_result or get_agent_context, so it falls short of a 5.

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?

Usage is only implied: an agent can infer this is the read-only status probe for local inference. The clause 'Performs no model start or network call' functions as a soft when-not (this is not the generation tool) but never names local_generate or any alternative, and there are no explicit prerequisites or exclusion conditions.

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