list_library_optimize

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

Annotations already provide read-only, idempotent, non-destructive behavior. The description adds only `GET /library/optimize`, which is redundant and conveys no additional behavioral context such as auth, pagination, or side effects.

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 very concise and front-loaded with no padding. The extra `GET /library/optimize` line is redundant but harmless, keeping the structure clean.

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 term 'Optimize Library' is never explained, so an agent cannot tell whether this returns a collection, statistics, or a specific resource. In a large sibling family with section-level optimize endpoints, this description is not complete enough for reliable tool selection.

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 zero properties, so there are no parameter semantics to explain. With no parameters, the description need not compensate for schema gaps, and the baseline for a parameterless tool is appropriate.

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 states a specific read verb ('Get') and a resource ('Optimize Library'), and the sibling tools `create_library_optimize` and `update_library_optimize` make the read/write contrast clear. However, 'Optimize Library' is undefined and 'Get' instead of 'list' adds slight ambiguity.

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 gives no guidance on when to use this tool versus siblings such as `get_library_sections_by_section_id_optimize` or `list_library`. It only states the endpoint and does not mention conditions, prerequisites, or alternatives.

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