get_award_report

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

Discloses that the endpoint uses a different id space, warns that wrong id returns a different contract, and implies read-only nature through 'Get' verb and report context. No annotations needed.

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?

Very concise: two sentences plus a brief caveat. Every sentence adds value with 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?

Given one parameter, no output schema, the description fully explains what the tool returns, the critical id caveat, and when to use an alternative. Sufficient for effective usage.

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 covers id with description, but the description adds crucial context: id is not proceso_compra.id, and explains how to obtain the correct id from a process detail payload.

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?

Explicitly states 'Get the richest award report for a process' and lists the fields included. Distinguishes from sibling get_process_detail via the caveat about id space.

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?

Provides explicit caveat about id space mismatch with proceso_compra.id, advises to obtain correct id from process detail payload, and recommends using get_process_detail when unsure.

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