Ver detalle de un trámite gubernamental

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

Annotations already declare readOnlyHint=true, openWorldHint=true and destructiveHint=false, so the safety profile is covered structurally. The description adds the content scope (what fields are returned) but discloses nothing about auth, rate limits, or failure behavior beyond that.

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?

A single front-loaded sentence with the resource first and the ID source trailing; every clause earns its place with no padding.

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 read-only tool with 100% schema coverage, full annotations and an output schema, the description needs only to identify the resource and where the ID comes from, which it does. It is essentially complete, with only minor room to note its distinction from the estadísticas sibling.

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%, so the baseline is 3, but the description adds genuine provenance for tramite_id by tying it to search_tramites, which helps an agent know where to obtain the required value. The format enum is left entirely to the 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?

States a specific verb+resource (get one gob.ec trámite) and enumerates what it returns: requirements, beneficiaries, cost and responsible institution. The singular 'One ... trámite' implicitly sets it apart from the sibling get_tramite_estadisticas, though it never names that sibling explicitly.

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 parenthetical '(tramite_id from search_tramites)' is a useful routing hint that this tool is a follow-up to search_tramites. However, it gives no explicit when-to-use/when-not guidance and never points to get_tramite_estadisticas as an alternative for a different need.

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