sei_marcar_processo

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

Annotations indicate a non-read, non-destructive mutation. Description adds behavioral context: it can add or alter, and removal via empty marker or marking with another. For a simple write tool, this is sufficient.

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 sentences plus a parameter list. No fluff, front-loaded purpose, every sentence earns its place. Highly concise.

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 output schema exists, description need not explain return values. Covers purpose, parameters, and removal behavior. Could mention overwriting behavior but not necessary.

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%, so description carries full burden. It explains all three parameters: processo (formatted protocol or ID), marcador (use sei_pesquisar_marcadores), texto (optional comment). Adds meaning beyond schema, though format of processo could be more precise.

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?

Description clearly states it adds or changes a colored marker on a process. Explicit verb and resource, and distinguishes from siblings like sei_consultar_marcador_processo (read) and sei_criar_marcador (create new marker).

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?

Explains when to use (add/change marker) and provides removal guidance (use empty or another marker). References sei_pesquisar_marcadores for finding IDs. Lacks explicit 'when not to use' but context with siblings implies alternatives.

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