escalation_basis

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

There are no annotations, so the description must carry the full burden of behavioral disclosure. It states the tool 'returns' legal basis, implying a read operation, but it does not explicitly declare side effects, permissions, or return format. The dependency on 'etapa' is mentioned, but other behavioral traits remain unexplained.

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, clear sentence that front-loads the action and object. It includes all necessary information without verbosity, effectively serving its purpose.

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 the tool's simplicity (one enum parameter, no output schema), the description provides adequate context about the content domain (legal bases for escalation). However, it lacks explanation of the parameter values and the structure of the returned legal basis, leaving some ambiguity for the agent.

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 description references 'según la etapa' which connects the parameter to the behavior, but it does not explain the meaning of the enum values ('escalamiento_secretaria' and 'amparo') or how they affect the output. With 0% schema description coverage, the description fails to compensate for the lack of parameter documentation.

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's function: it returns a complete legal basis for the escalation phase, listing specific laws (LFPDPPP, LFPA, Ley de Amparo, Constitución). The phrase 'según la etapa' indicates variability based on stage, distinguishing it from sibling tools that likely handle different granularity or purposes.

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 scopes the tool to the escalation phase ('para fase de escalamiento'), giving clear context for when to use it. It does not mention alternatives or conditions for when not to use it, but the context is sufficient for an agent to infer appropriate usage.

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