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

Annotations already cover safety (read-only, idempotent, non-destructive), so the bar is lower. The description's added context about output_count is inconsistent with a listing tool—it implies a parameterized generation behavior that isn't supported by the schema, confusing rather than clarifying the tool's actual behavior.

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 at two sentences, but the second sentence does not earn its place—it injects irrelevant and confusing generation semantics. A single-sentence description would be more concise and clearer.

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 template-listing tool with a schema and output schema, the core purpose is covered. However, the extra sentence creates ambiguity and overshadows completeness, suggesting capabilities the tool does not have. The description also doesn't explicitly state that these are headshot templates, though the tool name implies it.

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 input schema has zero parameters, which normally would receive a baseline of 4. However, the description introduces an 'output_count' parameter that does not exist in the schema, misleading the agent about potential inputs. This actively harms parameter understanding rather than adding value.

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 first sentence 'List predefined templates' clearly states a specific verb and resource. However, the second sentence about defaulting output_count introduces generation behavior that muddies the core purpose, causing slight ambiguity about whether this tool also generates headshots.

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 sibling tools like AI-Headshot-Generator or other template listers. The output_count note is a defaulting rule, not a usage criterion, and fails to distinguish this tool from alternatives.

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