abrir_no_computador

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

Discloses behavior: opens locally, reveal option, only within authorized folder. No annotations exist, so description carries full burden adequately.

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?

Three sentences, no wasted words. Front-loaded with main action. Could combine usage and restriction for slightly tighter structure.

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?

Covers main purpose, usage context, and constraints. Missing explanation of 'page' parameter and output behavior, but given tool's nature (local open), completeness is good.

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 has 0% description coverage. Description explains 'alvo' and 'revelar' (reveal=true reveals file), but 'page' and 'case_id' lack explicit explanation. Partial compensation.

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?

Description clearly states it opens PDF of page or full process on user's computer. Distinguishes from siblings like 'abrir_pagina' by specifying 'NO COMPUTADOR' and restricting to authorized folder.

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 quando o usuario quiser VER o original', providing clear context. Does not state when not to use or name alternatives explicitly, but sibling differentiation is implied.

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