buscar_grupos_produto

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

No annotations provided; description does not mention that this is a read-only operation, nor does it explain pagination (though 'pagina' parameter exists) or response format. Behavioral disclosure is minimal.

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?

Description is very short (two sentences plus note), front-loads the main purpose. Efficient, but missing essential parameter details.

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 3 parameters, no output schema, and 0% coverage, the description is insufficient. It explains neither input parameters nor output format, leaving the agent underinformed.

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% (no parameter descriptions), and the description adds no information about the parameters ('id', 'nome', 'pagina') or how to use them. The note implies 'id' might be used for filtering but is not explicit.

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?

Description clearly states the tool searches for product groups in Ploomes CRM and provides a use case (getting GroupId). However, it does not differentiate from sibling tools like 'buscar_familias_produto'.

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 note gives a specific context: use when creating or updating a product to get the GroupId. But no mention of when not to use or alternatives among siblings.

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