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

With no annotations, the description must carry behavioral load: it discloses the returned content categories and the prerequisite ('call this first'), implying a read-only discovery step. However, it never explicitly states read-only behavior, response size, or whether the catalog is static, leaving genuine gaps for a tool with zero annotation coverage.

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 content list and the 'call this first' directive are front-loaded and the mapping examples are compact and purposeful. The arrow-notation mapping sentence is somewhat dense but each element earns its place by showing real intent-matching examples.

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 parameterless catalog tool with no output schema, the description covers what is returned, the calling order, and how to use the preset mapping, which is close to sufficient. It stops just short of confirming read-only semantics or describing the shape of the returned entries.

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 per the baseline this is a 4. The description adds semantic value by explaining the data model interior to the catalog ('each preset has a for list') and how to map user words like 'quedada' to a preset, which goes beyond the empty schema.

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 enumerates exactly what the catalog contains (styles, occasion presets, block types with examples, envelope slots, stamps, seal options), so an agent knows what it will receive. It never states an explicit verb like 'returns' or 'lists', relying on a noun fragment, but the resource is unambiguous and clearly distinct from the letter CRUD 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?

'Call this first' is an explicit ordering directive that tells the agent when to invoke it relative to other tools, which is strong usage guidance. It does not name alternatives or exclusions (e.g., when it is unnecessary), so it falls short of a 5.

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