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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds substantive behavior context beyond that: the composite shape of a template (accounts, text, first comment, per-account privacy and made-for-kids settings) and how its identifier feeds create_post. Return ordering/count is not mentioned, keeping it at 4.

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?

Two sentences, no filler, with the content enumeration up front and the follow-up action second. The nested parenthetical listing account settings is a little dense but every clause carries information.

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?

For a zero-parameter read tool with a full annotation set and no output schema, the description covers what the items are and how to act on them. What is missing is minor — whether the list can be empty, its ordering, or pagination behavior.

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?

This tool takes no parameters, so the baseline is 4. The only identifier mentioned, template_id, belongs to create_post rather than this tool, but its mention usefully explains linkage between the two calls.

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 names the resource precisely — templates the owner saved in the app — and enumerates their contents (accounts, text, first comment, per-account options), so an agent knows exactly what comes back. The verb is only implied by the name, and there is no explicit contrast with siblings like list_posts or list_ideas, which keeps it from a 5.

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?

"Pass template_id to create_post to start from one" gives a concrete downstream action, which is exactly the context an agent needs to decide to call this. It does not state when not to use it or how it differs from other listing tools, so it falls short of explicit alternatives.

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