evite_list_templates

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

With readOnlyHint already indicating a safe read operation, the description adds value by disclosing the return format ('slug (= template_name) and a readable display name') and the meaning of the category parameter. It doesn't contradict annotations and provides enough behavioral context for a simple read-only 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 and front-loaded, starting with the main purpose, then providing parameter details and return info in a structured way. Every sentence carries meaningful information with no 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?

Despite having no output schema, the description explicitly states what the tool returns, making it complete for a simple list operation. It also situates the tool within the broader workflow by referencing evite_create_event, covering all necessary context for correct use.

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 coverage is 100% with both parameters already described, but the description adds critical meaning by explaining that the return slug serves as the template_name required by evite_create_event. It also elaborates on the category examples beyond the schema, enhancing agent understanding.

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 clearly states the tool's function: 'List invitation templates from a gallery category' with a specific verb and resource. It distinguishes itself from siblings by explicitly linking to evite_create_event, making its unique purpose unambiguous.

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?

It gives explicit usage guidance: 'use this to find the template_name that evite_create_event requires', which tells exactly when to use this tool. It also provides concrete category examples and explains the free_only option, giving the agent clear context for invocation.

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