describe_all_whitelist_template

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

Annotations already declare readOnlyHint=true, so the description's return type adds minimal value. No mention of potential pagination, rate limits, or empty results. The read-only behavior is adequately communicated by annotations.

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 short and front-loaded with purpose. It efficiently lists parameters and return type. Minor grammar issues ('whitelist template' vs 'whitelist templates') do not significantly detract.

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 tool's simplicity (2 params, read-only) and an output schema existing, the description covers basic functionality. However, it lacks guidance on usage and has a parameter description error, which reduces completeness for an agent.

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 description provides one-line explanations for both parameters, adding some meaning beyond schema titles. However, the description for template_name ('The ID of the RDS instance') is likely incorrect (it should be template name), potentially misleading. With 0% schema coverage, the description carries burden but does so inaccurately.

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 'describe all whitelist template' with parameters for region and optional template name, making the purpose clear. It differentiates from sibling tools like describe_instance_linked_whitelist_template by focusing on templates themselves. However, wording is slightly awkward and could specify that omitting template_name returns all templates.

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?

No explicit guidance on when to use this tool versus alternatives (e.g., describe_instance_linked_whitelist_template). The description does not indicate typical use cases or that template_name is optional, leaving the agent to infer from names.

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