sei_criar_documento_externo

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

Annotations are minimal (readOnlyHint=false, destructiveHint=false, openWorldHint=true) and consistent with description. Description adds significant behavioral details: file upload alternatives, size limit reference, naming importance, default values. No contradiction.

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?

Description is well-structured with bullet points, each sentence adds value. No redundant or filler content. Front-loaded with main action.

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?

Comprehensive parameter and usage details, references other tools. Does not mention return value, but output schema exists. Could be more complete with a note on return format, but still very thorough.

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 description carries full burden. It explains each parameter in detail: processo (format), id_serie (referenced to another tool), nivel_acesso (enum values), data_elaboracao (format), file upload parameters with usage scenarios. Adds meaning beyond 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 it creates an external document (upload file) in a SEI process, using specific verb and resource. It distinguishes from sibling tools like sei_criar_documento by specifying 'externo' and the upload context.

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 explicit guidance on when to use each file upload method (base64 vs path) and mentions using sei_pesquisar_tipos_documento for id_serie. Lacks explicit 'when not to use' but context is clear.

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