excluir_marcador

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

No annotations are provided, so the description carries the full burden. It states 'Excluir' (delete) which is destructive, but does not disclose whether the deletion is irreversible, if there are any side effects on related data, or if special permissions are required. For a deletion tool, this is insufficient.

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 very concise: two sentences and a prerequisite list. It is front-loaded with the purpose and gets straight to the point without any unnecessary words.

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?

For a simple delete operation with one parameter and no output schema, the description covers the core purpose and prerequisite. It could mention whether the deletion is reversible or any error conditions, but given the simplicity, it is largely adequate.

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?

There is one parameter 'id_marcador' with 0% schema coverage. The description does not explain the parameter but advises to obtain it via 'buscar_marcadores', which provides some context. However, it adds minimal semantic value beyond the parameter name.

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 'Excluir um marcador/tag do Ploomes CRM', specifying the verb (excluir) and resource (marcador/tag). This distinguishes it from sibling tools like 'excluir_cliente' or 'excluir_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?

Provides a clear prerequisite: first use 'buscar_marcadores' to obtain the ID. This tells the agent when to use this tool and what prior step is needed. It does not explicitly mention when not to use it, but the context is sufficient.

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