sei_listar_relacionamentos

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the description adds the version requirement and failure handling. It does not elaborate on what 'related' means or return format. With annotations providing the safety profile, the description contributes some behavioral context but not extensively.

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 lines) and front-loads the main purpose. Each sentence adds value: purpose, version requirement, and failure check. It could combine the last two lines for even greater 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?

With one parameter, annotations, and an output schema (not shown but exists), the description provides essential information. It explains the tool's action, version dependency, and recovery. It lacks output details, but the schema likely covers that, making it sufficiently complete for a simple list tool.

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 the description must compensate. It mentions 'processos relacionados a um processo', implying the parameter 'processo' identifies the process. This adds meaning but lacks format or example specifics. For a single required parameter, the context is partially helpful.

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 states 'Lista processos relacionados a um processo' (Lists processes related to a process), providing a specific verb and resource. It distinguishes itself from siblings like sei_listar_processos (general list) and sei_consultar_processo (detail view) by focusing on related processes.

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 includes a version requirement ('REQUER mod-wssei 3.0.2+') and failure recovery guidance ('Se falhar, use sei_versao para verificar'). It does not explicitly state when to use this versus alternatives, but the context provides reasonable clarity.

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