get_library_metadata_by_ids_users_top

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

The annotations already declare this as read-only, idempotent, and non-destructive. The description adds only the HTTP route and a terse summary, with no additional behavioral context such as authentication requirements, response semantics, or pagination behavior.

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 with the purpose, and contains no filler. It repeats the endpoint path that is already implied by the tool name, but overall it is efficiently structured.

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 the single parameter, the rich annotations, and the presence of an output schema, the description is minimally viable. The main gap is the ambiguous meaning of 'top users', which is not clarified anywhere.

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 schema provides only a bare 'Ids' string, so the description's 'Comma-separated list of IDs' adds useful format information. However, it does not clarify what kinds of IDs these are or how they relate to the endpoint's metadata path.

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 clear action and resource: 'Get metadata top users', and the HTTP path clarifies the endpoint. However, it does not explain what 'top users' means or how this tool differs from the many other get_library_metadata_by_ids_* siblings.

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 on when to use this tool versus alternatives, no mention of typical use cases, and no exclusions. An agent is left to infer usage purely from the name and endpoint.

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