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

Annotations already declare readOnlyHint=true and destructiveHint=false, but the description adds genuinely new behavioral context: the list is fixed and built into HookSend, no customer account is touched, and nothing is charged. It does not describe the returned shape, but the safety profile is more than adequately covered.

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?

Front-loads the purpose, then the workflow guidance, then the side-effect reassurance, in four compact sentences. Nothing is repeated from the title or restated tautologically.

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 no-argument read tool with no output schema, the description supplies what an agent needs: what it returns, how to consume the id, and that it is side-effect free. Only the precise content/shape of each template entry is left implicit, which is minor given no output schema is declared.

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?

Zero parameters, so the baseline is 4 and the schema already declares that it takes no arguments. The description adds cross-tool value by explaining what the returned template id is used for in flows_create, which the empty schema cannot convey.

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 a specific verb and resource ('Lists the ready-made flows') and immediately ties its output to a sibling's parameter ('the id flows_create takes as its template'). An agent can distinguish it from flows_list, flows_get, and flows_create without opening any schema.

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?

Gives explicit sequencing ('Call this before flows_create whenever the customer describes something a template already does') and names the follow-up call ('then flows_get the new flow'). It also states when not to bother writing from scratch, which is a real routing decision.

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