aya_templates_listar

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It only states what is listed, without revealing whether the operation is read-only, whether external template sources trigger network or filesystem access, or what side effects (if any) might occur. The term 'frozen' is not explained, leaving the behavior unclear.

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 sentence with no wasted words, making it efficient and front-loaded. However, the phrasing 'fontes de template externas e template visual congelado' is slightly cryptic and could be structured for easier parsing, though it remains appropriately brief.

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?

With no output schema and no annotations, the description should clarify what the tool returns and what key terms mean. It does not state whether it returns a list, a count, or an object, and it leaves 'external template sources' and 'frozen visual template' undefined. An agent calling this tool would still be uncertain about the expected output shape and the semantic scope of the listed items.

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 has zero parameters, so the baseline is 4. The description needs to explain no parameter semantics, and the empty input schema confirms there is nothing to document.

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 uses a specific verb, 'Lista' (lists), and names concrete resources: external template sources and a frozen visual template. It distinguishes itself from mutating siblings like aya_templates_congelar or validation-focused aya_templates_validar_hash, though the phrase 'template visual congelado' is somewhat domain-specific and could be clearer.

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 guidance about when to use this tool versus alternatives, nor any mention of exclusions or conditions. The description only implies that the tool is for listing, but provides no context about when it should be preferred over other listing tools like aya_toolsets_listar or aya_mcps_listar_permitidos.

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