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

Annotations already declare destructiveHint=true and idempotentHint=true; the description adds genuinely useful context by explaining that delete=true routes to Trash (not permanent), that a draft is required, and that templates are paid while profiles/deletes are free. This enriches the behavioral picture beyond the structured hints.

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?

It is a single run-on sentence cramming save, profile, storage location, delete behavior, prerequisite, and pricing into one breath. No filler, but the density hurts front-loading and parseability.

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?

An output schema exists, so return values need not be described, and the pricing/prerequisite details are helpful. Still, for a 6-parameter tool the description omits what name/subject do and gives no hint that it writes into a specific 'mailmcp-templates' location for the profile case beyond the quoted folder name.

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 only 33%, so the description must compensate. It does explain kind (profile = tone-only style) and delete semantics, but leaves account, name, and subject entirely undocumented in prose. Partial compensation justifies the baseline 3.

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 gives a specific verb+resource ('Saves a text template'), names the kind=profile variant, and covers the delete path via 'delete=true moves one mailmcp saved to Trash'. It clearly differs from the read-oriented list_templates sibling. It loses a point only because the phrasing is dense and the profile vs template distinction is squeezed into a single clause.

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 offers real context ('Needs draft; templates are paid, profiles and deleting free') that implies the prerequisites for calling it. However, it never states when to choose this over siblings like create_draft or list_templates, so 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.