buscar_templates_documentos

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

No annotations are provided, so the description must fully disclose behavior. It only states the purpose and that a TemplateId is obtained, but it does not mention whether the operation is read-only, the response format, pagination limits, or any safety details. This is insufficient for a tool with no annotation support.

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 very concise: a one-line purpose and a brief note. It is front-loaded and contains no fluff, though the note could be integrated into the main sentence. The structure is acceptable for a simple search tool.

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 the lack of output schema, annotations, and parameter descriptions, the description is incomplete. It provides minimal context for an agent to understand the full behavior, response structure, or how to apply filters. Sibling tools are listed but no differentiation is offered.

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 input schema has three parameters (id, nome, pagina) with zero description coverage in the schema. The tool description does not explain what these parameters do, how they affect the search, or their expected formats. This leaves the agent unable to use the parameters correctly without prior knowledge.

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 the tool searches for document templates in Ploomes CRM, and the note specifies its use to obtain a TemplateId when creating proposals or documents. While the name distinguishes it from the sibling 'buscar_templates_proposta' for proposal templates, the description could make this differentiation more explicit.

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?

The description includes a note on when to use the tool ('to obtain TemplateId when creating proposals or documents'), but it lacks guidance on when not to use it or how it compares to alternatives like 'buscar_templates_proposta'. This leaves the agent with incomplete decision-making information.

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