get_texto_operacion_expediente

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

No annotations are provided, so the description carries the full burden. It adds useful behavioral details like returning Markdown and preserving the E:/O: prefix, but omits side effects, error behavior, and authorization requirements. This is minimally adequate.

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 a single sentence that front-loads the purpose and immediately follows with the parameter usage instruction. No wasted words.

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?

For a simple one-parameter getter with no annotations and an output schema, the description is sufficiently complete. It covers what the tool does, the format of output, and exactly how to obtain and pass the required ID.

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 100% for the single parameter, establishing a baseline of 3. The description adds value beyond the schema by naming the exact source tools and emphasizing the need to preserve the prefix, making it more helpful than a bare 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 verb 'Get', the resource 'text content of an operation within an expediente', and the output format 'Markdown'. It distinguishes itself from siblings by explaining that the ID comes from get_operaciones_expediente or get_adjuntos_expediente.

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 explicitly instructs to pass the idOperacion exactly as returned by get_operaciones_expediente or get_adjuntos_expediente, providing a clear prerequisite and source for the parameter. It does not mention exclusions or alternative tools, but the context is sufficient for proper use.

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