salvar_peca_produto

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

No annotations provided, so description bears full burden. It mentions mutability but lacks details on side effects, permissions, reversibility, or what happens with missing optional fields. The relationship between 'id' and 'peca_produto_id' is confusing.

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 concise sentences that directly state the function and a key usage note. No unnecessary words, but structure could be improved by front-loading the core action.

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 and no annotations; description does not cover return behavior, validation rules, or relationships to sibling tools. The tool has four parameters, but only one is partially mentioned.

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% and description adds no explanation for the four parameters. The text does not clarify the meaning of 'id', 'produto_id', 'quantidade', or 'peca_produto_id', leaving the agent to infer from schema alone.

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?

Clearly states it creates or updates a product part/component in Ploomes CRM, and the sibling tool 'excluir_peca_produto' indicates the delete counterpart, so purpose is well-defined.

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?

No guidance on when to use this tool vs other tools (e.g., excluir_peca_produto for deletion). The instruction 'Passe o ID para atualizar uma peca existente' is vague and does not clarify when to provide an ID versus not.

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