catalog_get_catalog_items

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

The annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=true, so the safety profile is covered. The description adds that results are paginated, but it does not discuss authorization requirements, rate limits, or the shape of returned catalog items beyond calling it a list.

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 and front-loaded with the core purpose. It has minor redundancy between 'Fetch a list' and 'Returns a paginated list,' and the raw GET endpoint is not necessary for an agent, but the overall structure is efficient.

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 has 11 optional filtering/pagination parameters, but the schema documents them fully and annotations cover read-only behavior. However, with no output schema, the description could say more about the returned catalog item structure, pagination metadata, or how this differs from admin listing tools, leaving clear gaps.

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 every parameter is already documented in the input schema, including filters like search, types, projects, sort, and pagination fields. The description adds no parameter-specific meaning, which is acceptable given the high schema coverage but does not exceed the baseline.

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 verb and resource: fetch a list of catalog items. It is specific enough to understand the operation, but it does not distinguish itself from closely named siblings such as catalog_get_catalog_items_for_admin or catalog_get_catalog_item.

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 provides no guidance on when to use this tool versus alternatives. With many catalog-related siblings, an agent must infer whether this is the general user-facing list endpoint or the admin variant, and no exclusions or selection criteria are given.

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