sei_excluir_marcador

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

The description is consistent with annotations (destructiveHint: true) but adds no extra behavioral context beyond what annotations already provide. It does not disclose results, side effects, or permission requirements.

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?

Extremely concise (one short sentence) and front-loaded with the primary action. However, it could include a brief note on usage or behavior without losing conciseness.

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 the low complexity (1 parameter, no nested objects, output schema exists), the description is adequate. However, it omits details like whether non-existent IDs are handled gracefully, or if the operation is irreversible (though destructiveHint suggests it).

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 only parameter 'ids_marcadores' is described as 'IDs separados por vírgula', clarifying the expected format (comma-separated) and cardinality (multiple IDs allowed). The schema only specifies type string, so the description adds valuable semantic detail.

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 action (excluir) and resource (marcador), with additional detail on the input format (IDs separados por vírgula). It distinguishes itself from sibling tools like sei_criar_marcador and sei_marcar_processo.

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 versus alternatives (e.g., sei_desativar_marcador for deactivation), nor any prerequisites or contexts. The description only states what it does, not when to invoke it.

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