buscar_secoes_campo

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

No annotations are provided, so the description shoulders full responsibility for behavioral transparency. It lacks details on whether the tool is read-only, destructive, or its side effects. There is no mention of pagination, return format, or error behavior, leaving significant gaps for an agent.

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 short (three sentences) with a clear title-like first sentence and two bullet points that are directly informative. Every sentence adds value, though more structured formatting could improve scanability.

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 no output schema and no annotations, the description is insufficient. It lacks details on output structure, pagination handling via 'pagina', and the role of 'nome' parameter. A more complete description would clarify expected results and usage nuances.

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 description coverage is 0%; the description adds little beyond the schema. Only 'entidade_id' is briefly mentioned in observation 2 as a filter, but 'nome' and 'pagina' are not explained. This provide marginal additional meaning over the bare schema.

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 states 'Buscar secoes de campos personalizados no Ploomes CRM,' which clearly identifies the action (search) and resource (sections of custom fields). However, it does not explicitly differentiate from sibling tools like 'buscar_campos' or 'salvar_secao_campo,' though the purpose is distinct enough.

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 two observations: using it to obtain SectionId when creating custom fields, and filtering by entidade_id for specific entity sections. This provides clear context and a primary use case, but does not mention when to avoid using the tool or alternative tools.

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