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

The description says 'List' and 'No personal data required', strongly implying a read-only, privacy-safe operation. However, annotations declare readOnlyHint=false, which contradicts the inherently read-only nature of listing options. This is an annotation contradiction that undermines behavioral transparency.

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 a single, front-loaded sentence with a clear verb, an enumerated resource list, and a useful privacy note. There is no filler or redundancy.

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 zero-parameter tool with no output schema, the description fully covers what the tool lists and the fact that no personal data is required. An agent can invoke it without additional clarification, aside from the separate annotation contradiction issue.

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 has zero parameters and 100% schema description coverage, so the schema is already complete. The description adds no parameter details, but none are needed; this matches the baseline for a 0-parameter tool.

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 uses the specific verb 'List' and names the exact resources: greeting languages, occasions, styles, image formats, and background categories. This clearly differentiates it from action-oriented siblings like create_greeting_card and generate_greeting.

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 implies the tool is for exploring available options before creating or generating greetings, and the phrase 'No personal data required' adds useful context. However, it never explicitly states when to use this tool over its siblings or when not to use it, so the usage guidance remains implied rather than explicit.

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