mailkite_list_base_templates

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

Annotations include readOnlyHint=true, so the description doesn't need to restate that. It adds that it returns light metadata (implying not full template) and requires a management session token, which is useful. However, it doesn't specify pagination or output structure beyond light metadata.

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 concise, two sentences, with no fluff. It front-loads the purpose, then provides actionable next stepsable (clone or send) and the prerequisite (management session token). Every word earns its place.

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?

Given it's a simple list operation with no params, the description is quite complete. It mentions the output (light metadata) and the use cases, and the annotation covers read-only. The only gap is the structure of the output (e.g., fields), but that is minor for a list of base templates.

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 no parametersujetes (0 params), so the schema is empty. The description adds value by explaining the return type (light metadata) and how the results can be used, which compensates for the lack of parameter details. Since there are no params, a baseline of 4 is appropriate.

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 it lists base templates with light metadata, and distinguishes it from sibling tools like mailkite_list_templates (which likely lists all templates). It also mentions cloning or sending directly, giving a clear purpose.

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 when to use it: when you need to browse premade templates. It mentions actions (clone or send) but doesn't explicitly state when not to use it or alternatives (e.g., mailkite_list_templates). The context signal of having siblings is high, but no explicit exclusion is given.

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