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

The annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered without the description. The description adds nothing beyond that: it says nothing about pagination behavior, result ordering, whether the list is org-wide or permission-scoped, or how many items to expect. It does not contradict the annotations, but it is purely restating the name.

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 with zero filler or redundancy. It is efficiently written, though its brevity reflects under-specification rather than disciplined editing, which is penalized in the other dimensions.

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?

The tool is simple: no required parameters, strong read-only annotations, and an output schema that documents the return shape, so the agent can plausibly invoke it. The gaps are the unstated pagination contract and the missing distinction from list_location_resources, which for an organization with many similarly named list tools is a real risk.

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 description coverage is 0%, so neither limit nor offset is documented anywhere, and the description does not mention pagination at all. The parameter names and the schema's defaults and bounds (limit 1-100 default 25, offset 0-10000 default 0) make their conventional purpose inferable, which keeps this above a 1, but the description contributes no semantics of its own.

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 pairs the verb 'List' with a specific resource, 'the organization's resource library,' so the agent knows exactly what collection is returned. It does not, however, differentiate this tool from close siblings such as list_location_resources, get_resource, or download_resource, leaving the agent to infer scope on its own.

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 when-to-use guidance, no mention of when to prefer list_location_resources (location-scoped resources) or get_resource (single item), and no stated prerequisites. For a listing tool the usage is loosely implied, but nothing in the text resolves the overlap with its siblings.

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