Find ZeptoMail templates

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint, so the safety profile is covered. The description adds useful behavioral context beyond that: the scope of the search with and without agentKey, and that results always include the owning Agent.

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?

Three sentences, each earning its place: the search action, the scoping behavior, and the guaranteed result field. No redundancy or filler.

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 the safe annotations and simple parameter set, the description covers the essential behavior: what is searched, how to scope the search, and what results always include. The absence of an output schema is partially mitigated by the 'owning Agent' note, though full result shape is still not described.

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%, but the description compensates by explaining that query searches name, alias, and subject, and by clarifying agentKey's optionality. maxResults is not mentioned, though its schema defaults, min, and max make its behavior reasonably inferable.

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 opens with a specific verb and resource: 'Search template name, alias and subject.' It clearly separates this search-oriented tool from sibling list/get/create/update/delete operations, and the agentKey scoping further sharpens its 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 gives clear context for use: omit agentKey to search all accessible Agents, or provide it to restrict to one Agent. It does not explicitly name alternatives or state when not to use the tool, but the search scope guidance is straightforward.

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