catalog_get_versions_for_admin

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, so the safety profile is covered. The description adds that results are paginated and exposes the endpoint path, but says nothing about admin authorization requirements or what happens when the id does not exist — the most relevant missing behavior for an admin endpoint.

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?

Three short lines, front-loaded with the action and resource, no filler. The first two sentences are somewhat redundant (both restate 'list of ... versions'), which is the only wasted text.

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?

With no output schema, the description should ideally say what a version record contains or how results are ordered/filtered; it only says 'paginated'. Annotations cover safety and the schema covers parameters, but the admin-vs-standard distinction remains unexplained.

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 100%, so id (UUID), page, size and sort are all documented in the schema itself. The description adds no syntax or constraint detail beyond that, so baseline 3 applies.

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?

States a clear verb (fetch/list) and resource (catalog item versions) plus the underlying REST path, so the agent knows exactly what it retrieves. However, it never distinguishes itself from the sibling catalog_get_versions, and the first sentence ('list of catalog items with versions') is slightly inconsistent with the second ('list of catalog item versions' for a given {id}).

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 on when to use this admin-scoped variant versus catalog_get_versions, catalog_get_version_by_id, or catalog_get_version_by_id_for_admin, all of which appear as siblings. The 'admin' qualifier implies elevated scope but the description never states the selection condition.

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