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

With no annotations, the description carries the full burden of behavioral disclosure, but it is minimal. It says 'Retrieves', implying a read operation, but does not explicitly state that it does not modify data, nor does it describe the return format, potential pagination, or any side effects. For a listing tool, the lack of information about what is returned (e.g., full objects vs. summaries) is a gap.

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 a single concise sentence with no filler. It front-loads the core purpose, lists the specific template types, and specifies the scope. 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 no output schema, the description should explain what the tool returns (e.g., a list of template objects, or summaries), but it does not. It also omits any mention of pagination, ordering, or authentication requirements. For a simple listing tool, however, the core functionality is clear, but the missing return details make it less than fully 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?

Schema coverage is 100%, so both parameters (agentId and accountId) are already described in the schema. The description adds no extra meaning beyond the schema, such as how agentId is used or what 'automatically scoped' means for accountId. Baseline of 3 is appropriate when schema already documents all parameters.

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 a specific verb ('Retrieves') and resource ('pre-configured rich media, card, carousel, and text message templates') scoped to 'an agent profile'. It distinguishes itself from siblings like create_template (creation) and get_template_detail (single template) by indicating a plural list retrieval, so an agent can tell it apart without opening schemas.

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?

There is no explicit guidance on when to use this tool versus alternatives. The description does not mention that for a single template one should use get_template_detail, or that create_template is for creation. It only implies the action of listing, leaving the agent to infer appropriate usage. Given the existence of closely related siblings, more explicit routing would be valuable.

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