get_provider_status

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so "No remote account checks" largely restates the closed-world annotation rather than adding new behavior. Useful reinforcement for a status call, but it does not disclose what is inspected (config files, env vars, credentials presence) or what happens when no providers are configured.

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 short, front-loaded sentences with no filler — scope first, boundary second. It is efficient, though the terseness trades away the detail an agent would need to interpret the result, so it stops just short of ideal.

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-param probe with no output schema, the description should at least sketch what the returned status contains (e.g., available providers, configured/unconfigured flags). It establishes the local-only limitation but leaves the response shape and failure modes unspecified.

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. No misleading parameter language is present.

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?

"Inspect" plus "local library and configured optional providers" gives a verb and object, but the object is ambiguous — "this local library" and "providers" are undefined, and the tool name's promise of a *status* result is only implied. It is not a tautology, but an agent would not confidently know what it is querying or how it differs from the configuration-related siblings.

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 clause "No remote account checks" implies a scope boundary and, weakly, a when-not (don't use this to validate remote/provider accounts), which is real implied guidance. However, no sibling is named as an alternative, and there is no explicit statement of when a caller should reach for this versus the many other list/get tools.

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