get_expediente

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

With no annotations, the description bears full transparency burden. It discloses that the response includes a `partes` block, `ladoUsuario`, `esUsuario`, and a fallback where `partes` is null with an error reason. It also implies authentication context via the user's matrícula. It doesn't mention behavior for 'not found' but covers key state.

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?

Every sentence is information-dense and earns its place: action, usage timing, return structure, field semantics, fallback behavior, and downstream guidance. There is no redundant fluff, and the main verb is front-loaded.

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 no output schema, the description fully explains the return shape and behavioral nuances (partes block, ladoUsuario, esUsuario, partesError). It also places the tool in the larger workflow by linking to sibling tools. This is sufficient for an agent to invoke it and interpret results.

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 already describes both parameters (100% coverage), but the description adds the crucial relationship: either numeroExpediente OR idExpediente is used, and idExpediente is the internal ID to be passed to downstream tools. This adds meaning beyond the schema's individual field descriptions.

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 ('Look up'), the resource ('a single expediente'), and the key identifiers ('numeroExpediente OR idExpediente'). It distinguishes itself from the sibling tool get_expedientes by implying singular vs. plural use.

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?

Explicitly says 'Use this at the start of any chat about a case' and directs the agent to use the returned idExpediente with subsequent tools (get_operaciones_expediente, get_adjuntos_expediente). It doesn't explicitly list exclusions, but the context clearly implies when it is appropriate.

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