list_library_random_artwork

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

Annotations already carry readOnlyHint, idempotentHint, and destructiveHint: false, so the safety profile is already established. The description adds the GET endpoint and the notion of randomness, but does not clarify how randomness affects returned values or how the optional sections scope the selection. No contradiction with the annotations.

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?

The description is short, front-loaded, and has a clear structure: action statement, endpoint, then parameter. The endpoint line is somewhat redundant with the action statement but still adds the canonical path; no filler is present. It is concise without being degenerate.

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?

Given a read-only tool with a single optional parameter and an output schema, the description does not need to explain return values. But the only non-trivial input is under-described, and the scoping and randomness semantics are left to inference, leaving an agent to guess on the one decision it must make.

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 input schema has 0% schema description coverage, and the description's one line, 'The sections for which to fetch artwork,' does give the parameter a purpose. However, it does not specify what the array items should be, whether omitting sections means all sections, or how section identifiers are represented.

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 opens with a specific verb and resource, 'Get random artwork,' and the endpoint 'GET /library/randomArtwork' confirms the operation. The word 'random' makes it easy to distinguish from sibling library listing and art-related tools, so an agent can identify what this tool does.

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 guidance about when to choose this tool over list_library, get_library_sections_by_section_id_arts, or other library endpoints. The only usage signal is the bare action statement; no prerequisites, exclusion cases, or alternatives are named.

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