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

Annotations already establish read-only, non-destructive behavior, lowering the burden on the description. The description adds meaningful scope context—global catalogue, used across event certificate configs—which helps the agent understand the returned data's role. It does not detail pagination or response format, but those are less critical given the full parameter schema.

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 key fact that this is a global catalogue. The final fragment 'Not tied to one event' restates 'global' slightly, but the parenthetical about the background field is valuable and keeps it compact.

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?

For a simple list operation with zero required parameters and fully described pagination schema, the description gives enough context about what the collection represents. A small gap is the absence of any mention of the response shape or ordering, but no output schema exists and the resource type is clear.

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% and the two parameters (page, page_size) have complete descriptions. The tool description adds no parameter-specific semantics, so the schema carries the full burden; baseline 3 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 identifies a specific resource ('certificate background templates') and defines the operation as listing the global catalogue. It also clarifies the domain purpose ('background field of an event's certificate config') and explicitly differentiates from event-scoped resources by saying 'Not tied to one event.'

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?

It conveys that this is the global, event-independent catalogue, which implies using it when you need certificate backgrounds not attached to a particular event. It stops short of naming alternative sibling tools or giving explicit when-not-to-use conditions, so it is clear context rather than explicit routing.

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