salvar_origem_contato

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

No annotations are provided, so the description carries full burden. It discloses a create/update operation but lacks details on side effects, permissions, rate limits, or return behavior. The agent has little insight beyond the basic action.

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 concise: two sentences with no extraneous information. The first sentence states the purpose, the second adds a key usage hint. Every word earns its place.

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 only 2 parameters and no output schema, the description is somewhat complete but lacks details on the 'nome' parameter, behavior when id is null, and what the tool returns. It could be more helpful for an agent.

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%, so the description must add meaning. It explains the 'id' parameter's role (used for updates). The 'nome' parameter remains unexplained beyond being required. This adds some value but is minimal.

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 creates or updates a contact origin in Ploomes CRM (verb and resource). It distinguishes from siblings by the specific resource, though it does not explicitly differentiate from other 'salvar' tools.

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 provides basic usage guidance: 'Passe o ID para atualizar uma origem existente' implies when to use ID. However, no exclusions or alternatives are mentioned, such as when to fetch existing origins via buscar_origens_contato.

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