refresh_library_metadata

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

With no annotations provided, the description carries full responsibility. It indicates a mutation ('Refresh') and an admin permission, but does not disclose side effects, whether existing metadata is overwritten, potential performance impact, or what happens on failure. Minimal behavioral information beyond the action itself.

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 a single sentence with no redundant information. It front-loads the core action and includes the important admin requirement. 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?

The tool is simple (one parameter, output schema present), but as a mutation it lacks information about the refresh process, what embedded metadata means, and any side effects. The description is minimally viable but leaves gaps for an agent deciding whether to invoke it safely.

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 0%, so the description must compensate. It mentions 'for a library', clarifying that library_id is the ID of the target library. However, it provides no additional detail about the parameter format or how to obtain it. For a single obvious parameter this is sufficient but not rich.

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 clearly states the tool refreshes embedded metadata for a library. The verb 'refresh' and resource 'library metadata' are specific, and it distinguishes from sibling tools like refresh_book_metadata and refresh_series_metadata by targeting the library level.

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 guidance is given on when to use this vs alternatives such as scan_library or analyze_library. The admin requirement is mentioned but does not explain the appropriate scenarios or when to avoid this tool. Usage context is only implied by the name and description.

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