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

The annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is fully covered. The description adds 'Reads only,' which is redundant with the annotations, and gives no additional behavioral context like pagination or return format. With annotations covering behavior, a 3 is appropriate for adding essentially nothing new.

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?

Very concise: a single sentence fragment. The information is front-loaded. It could be slightly more informative without becoming verbose, but it earns its place by stating scope and read-only nature.

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?

The tool is simple (no params, no output schema), and the annotations cover the safety profile. However, the description does not tell the agent what the return contains (e.g., list of names), nor does it differentiate from siblings like report_template_get. For a minimal tool, it's adequate but lacks the sibling routing that would make it complete.

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?

There are no parameters, so the baseline is 4. The description adds no parameter information because none exists, which is correct.

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?

States the resource clearly ('saved report templates, by name') and the verb 'list' is implied by the title. The title 'Report templates: list them' is more explicit, but the description itself doesn't state the action verb. Sibling tools like report_template_get and report_template_delete exist, so it's distinguishable, though the description could explicitly say 'list'.

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 when-to-use or when-not-to-use guidance. It doesn't mention alternatives like report_template_get (for a specific template) or how it relates to report_style or report_template_save. The sibling context makes the need for differentiation greater, but none is provided.

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