buscar_formulario_proposta

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

No annotations provided, so the description carries the full burden. It explains the returned structure (FormField items), distinguishes block fields (QuickFormId) from common fields (FieldKey), and mentions product filter attributes. No performance or error details, but the behavioral disclosure is good.

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?

Concise and well-organized with numbered notes. Every sentence adds value, no redundancy. Front-loaded with the main purpose, then details in structured bullets.

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?

No output schema, so description must explain return structure, which it does adequately (FormField items with FieldKey/QuickFormId). Also covers block filtering attributes. Does not mention error cases or null parameter behavior, but is largely complete for a fetch tool.

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?

Schema coverage is 0%, but the description fully explains both parameters: template_id for top-level form, form_id for specific form or recursive block drill-down. Adds practical usage context that the schema alone lacks.

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 fetches the form structure of a proposal/sale/document model. It specifies two distinct usage paths: by template_id or form_id, and distinguishes from sibling tools like buscar_templates_documentos.

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?

Provides explicit guidance: use template_id for the main form, form_id for specific forms or to dive into blocks. Recommends buscar_templates_documentos to get template_id. Explains the difference between FieldKey and QuickFormId fields, helping the agent decide when to call recursively.

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