Formatear cita chilena

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

With no annotations provided, the description carries full burden. It indicates a non-destructive formatting operation and data integrity constraint ('No inventa datos'), but lacks details on input validation, error behavior, or authentication requirements.

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?

Two sentences, no filler, front-loaded with key purpose and constraint. Every word earns its place.

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 16 parameters, no output schema, low schema coverage, and no annotations, the description is too brief. It does not explain output format, parameter dependencies, or which identifiers are required for different citation types, leaving the agent underinformed.

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?

The schema has 16 parameters with only 6% description coverage. The description only mentions high-level identifier types (norma, ROL, dictamen, doctrina), failing to explain the meaning of each parameter or how they combine to produce the citation. This is insufficient given the parameter count.

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 generates a formal citation string using already retrieved identifiers. The verb 'Genera' and resource 'cadena de cita formal' are specific, though it does not explicitly differentiate from sibling tool 'citar_texto_legal' which may also handle citation formatting.

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 restricts usage to already retrieved identifiers ('SOLO con identificadores ya recuperados') and warns against inventing data. This provides clear context but does not mention alternatives among sibling tools.

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