evite_list_templates

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

Annotations already declare readOnlyHint=true. The description adds useful behavioral context beyond that: it returns each template's slug (= template_name) and display name, explains the category path format, and notes the free_only filter. It does not cover pagination or rate limits, but that is not critical for this read-only listing tool.

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 compact, with the core purpose and usage front-loaded. Each sentence earns its place: purpose plus integration with evite_create_event, category examples, and return value semantics. 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 read-only template listing tool with three parameters and no output schema, the description covers the essential context: what it returns, how category paths look, and the free_only behavior. The view parameter is fully described in the schema, so the description need not repeat it. Minor gaps are lack of pagination or volume expectations, but these are not required for correct invocation.

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%, so the baseline is 3. The description adds only marginal value beyond the schema: one extra category example and the semantic link between slug and template_name. The view and free_only parameters are already well described in the 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 states a specific verb and resource: 'List invitation templates from a gallery category.' It clearly distinguishes the tool from event/guest/message siblings and explains its role as the source of template_name for evite_create_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?

The description explicitly says to use this tool to find template_name for evite_create_event, which is clear context. It does not explicitly state when not to use it or name an alternative, but no sibling tool provides template listing, so the guidance is sufficient.

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