salvar_grupo_produto

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

Describes basic upsert behavior but lacks details on side effects, idempotency, or what happens if ID does not exist. With no annotations, more behavioral context is needed.

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?

Two front-loaded sentences with no wasted words. Directly states purpose and usage condition for ID.

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?

Covers basic create/update distinction but omits return values, error conditions, or field constraints. For a simple tool with no output schema, additional context on behavior would improve completeness.

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?

Adds meaning for 'id' (optional for create, required for update) beyond schema. 'nome' is implied as the group name but not explicitly described. Schema coverage is 0%, so description partially compensates.

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 creates or updates a product group ('criar ou atualizar um grupo de produto'), distinguishing it from sibling tools like 'buscar_grupos_produto' (search) and 'excluir_grupo_produto' (delete).

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?

Implies when to use: pass ID for update, omit for create. However, no explicit mention of when not to use or comparison with sibling tools like 'buscar_grupos_produto' for retrieval.

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