sei_criar_contato

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

Annotations indicate readOnlyHint=false, destructiveHint=false, and openWorldHint=true. The description adds minimal behavioral context beyond the version check advice. It does not discuss side effects, required permissions, or what happens on creation (e.g., duplicates).

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 short (three sentences) but includes a version note and troubleshooting advice that, while helpful, could be better placed elsewhere. It lacks parameter explanations, which would be more impactful in the same space.

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?

With an output schema present, the description doesn't need to explain return values, but it fails to provide essential context about parameters (valid values, mandatory ones) or the creation process (e.g., error handling beyond version check). The tool feels underdescribed for a creation operation.

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 should compensate, but it mentions no parameters. The four parameters (nome, tipo, email, telefone) are left entirely for the agent to infer from names. The description adds zero semantic value beyond the schema.

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's purpose: 'Cria novo contato no SEI.' It uses a specific verb (cria) and resource (contato). Among siblings, there is a search tool (sei_pesquisar_contatos) but no other create contact tool, so it is distinct.

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 no guidance on when to use this tool versus alternatives. It only includes a version availability note and a troubleshooting hint about checking version on error. No context on prerequisites or when not to use.

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