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

Annotations already declare readOnlyHint=true, idempotentHint=true, openWorldHint=false, and destructiveHint=false, so the safety profile is covered. The description adds useful context about the returned content — per-provider credential fields, acquisition instructions, and live connection status. It adds some value but says nothing beyond annotations about scope (all providers vs. only connected ones) or freshness/caching.

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 that front-loads the resource and packs in the three return concerns (availability, required fields, connection state). No filler or repetition.

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, and read-only annotations, the definition needs only to communicate what the listing contains and why an agent would call it — which it does. The only gap is that it doesn't clarify whether unconnected providers are included or point to the sibling that performs the connection.

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 the baseline is 4; there are no parameter semantics to explain. The phrase 'the fields it needs and how to get them' refers to returned data rather than inputs, which is consistent with the empty schema.

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 names the specific resource — AI providers and coding tools whose billing Veqen can read — plus the extra data returned (required fields, how to obtain them, connection status). It is a noun phrase rather than a verb phrase, so it reads as a description of results rather than an action, but combined with the name an agent can identify what it returns. It implicitly distinguishes itself from connect_provider/disconnect_provider, which act rather than list.

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 statement of when to call this tool versus connect_provider, disconnect_provider, or list_provider_keys. No prerequisites, no exclusions, no routing guidance — the agent must infer from the name that this is the 'what can I connect and what is already connected' inventory call.

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