Api stored libraries provider retrieve

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description adds nothing beyond that — it doesn't say what the response contains (a list of provider keys?), whether it's static choice metadata, or whether openWorldHint implies external lookups.

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?

There is nothing to trim, but this is under-specification rather than conciseness: a lone identifier-shaped token gives the reader no front-loaded intent. Any single sentence of real content would have improved it at no cost.

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-parameter, read-only, idempotent lookup with full annotation coverage and no output schema, an agent needs almost nothing more. The remaining ambiguity about the return shape is minor and partly inherent to a choice/enumeration endpoint. This score reflects adequacy, not strength — the description itself is still empty.

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 empty input schema is the complete contract and the description carries no parameter burden. Baseline 4 applies.

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 is the tool name restated verbatim ('api_stored_libraries_provider_retrieve') with no added phrasing. An agent can infer from the identifier that it retrieves a 'provider' value related to stored libraries, but there is no verb+resource statement and no differentiation from siblings such as stored_libraries_locale_retrieve or stored_libraries_object_type_retrieve, which follow the identical pattern.

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?

No when-to-use, prerequisites, or alternative-selection guidance is given. The agent must guess whether this is the endpoint that enumerates valid 'provider' choices for stored libraries or something else entirely.

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