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

No annotations are provided, so the description carries the full burden. It lists what the catalog contains but says nothing about read-only nature, side effects, authentication, or response format. The 'get' name implies a read, but that is not stated, leaving the agent to infer safety.

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?

Two short sentences with no filler; contents are front-loaded and the usage directive follows. Efficient and appropriately sized for a simple catalog tool.

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 tool's simplicity (no parameters, no annotations, no output schema), the description is largely complete: it lists the catalog's contents and tells when to call it. It could be improved by explicitly stating that it returns a static read-only reference, but the essentials are present.

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 tool takes zero parameters, so the schema provides no parameter info. The description adds nothing about parameters, which is appropriate for a parameterless tool. Baseline 4 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?

The description names the resource (catalog) and enumerates its contents (styles, presets, block types, etc.), making the tool's purpose clear. However, it lacks an explicit verb like 'returns' or 'lists'—the retrieval action is only implied by the tool name. Siblings are distinct (letter CRUD), so no differentiation is needed.

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?

Explicitly states 'Call this first to compose a letter,' giving clear timing and context for use. It does not mention when not to use it or name alternatives, but for a singular catalog tool no alternatives exist.

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