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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so safety is covered structurally. The description adds no behavioral detail about the result set — ordering, whether archived/system templates are included, or pagination. The closing "agente = ..." sentence explains a domain concept about agents rather than this tool's behavior, so it contributes little here.

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?

Three short sentences, front-loaded with the resource definition and then the actionable workflow hint. The final sentence about agents is tangential to listing templates and is the only part that does not clearly earn 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?

For a zero-parameter read tool with annotations covering safety and no output schema, the description is sufficient: it explains the resource, says when to call it, and signals that template_id is returned for use in create_process. Only the exact shape of the returned list remains unstated, which is minor.

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 tool takes zero parameters, so there is nothing for the description to disambiguate and the baseline applies. It correctly signals no filtering is required to call it.

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 gives a specific verb and resource ("Lista os templates de processo") and goes further by defining what a template is with a concrete example ("checklists reutilizáveis, ex: 'Onboarding de Cliente Novo'"). That definition implicitly separates it from list_processes (instances) and create_process_template, though no sibling is named outright.

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?

It states a clear when-to-use: "Use antes de create_process para pegar o template_id," which ties invocation to a concrete downstream workflow. No when-not-use condition or alternative lister is mentioned, so it stops short of the top band.

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