variable_library_list

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

Annotations already declare readOnlyHint=true and destructiveHint=false, covering the safety profile. The description adds the workspace scoping and 'all' behavior, but it does not disclose pagination, ordering, or whether the results are summaries or full definitions.

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 states the action, resource, and scope with no filler. Every word earns its place.

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 one-required-parameter, read-only list operation, the description is nearly complete: it states what is listed and the scope. It would be fully complete with an explicit note about the result shape, but the tool's low complexity and schema coverage make the current description sufficient.

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?

Schema coverage is 100%, and workspaceId is already documented as 'The workspace ID'. The description's 'in a workspace' aligns with this parameter but adds no new format, default, or edge-case semantics.

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 uses the specific verb 'List' with the resource 'variable libraries' and scopes it to 'a workspace', making the operation unambiguous. Among siblings like variable_library_get and variable_library_create, the plural 'all variable libraries' clearly identifies this as the enumeration tool.

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 description implies use when an agent needs to enumerate all variable libraries in a workspace, but it does not explicitly say when to prefer this over variable_library_get or mention any exclusions. No alternative tool is named.

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