salvar_marcador

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

The description states it creates or updates, which implies mutation but does not disclose further behavioral details such as idempotency, required permissions, or side effects. Since no annotations are provided, the description carries the full burden; it is adequate but not comprehensive for a mutation tool.

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 and well-structured: a main sentence followed by bullet points with key observations. Every sentence provides useful information without redundancy.

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, the description adequately covers purpose and key parameter hints, but does not describe the return value (e.g., does it return the created/updated tag?). This omission leaves the agent uncertain about the tool's output format.

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?

The input schema has 4 parameters with 0% coverage. The description explains the 'id' parameter (pass to update) and 'entidade_id' (with mapping), but does not explain 'nome' or 'cor' beyond their schema titles (which are self-explanatory, but the description adds no extra context). It adds value for some parameters but not all.

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 'Criar ou atualizar um marcador/tag no Ploomes CRM.' It specifies the verb (criar/atualizar) and resource (marcador/tag), and differentiates from sibling tools like 'buscar_marcadores' and 'excluir_marcador' by mentioning how to obtain the ID for updates.

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 guidance on when to use this tool (create or update) and explicitly advises using 'buscar_marcadores' to get the ID for updates. It also includes a mapping for 'entidade_id' values (1=Clientes, etc.), which helps the agent use the parameter correctly. However, it does not give explicit 'when not to use' instructions.

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