open_file

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

No annotations are provided, and the description only says 'Open a file...' without disclosing potential side effects, permissions required, or what happens if the application is not found. This is a side-effecting action but the description carries no additional behavioral context.

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 concise and front-loaded with the purpose, followed by the args section. It is two lines and wastes no words, though the args section repeats schema titles.

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 tool that opens a file, the description is minimal. It does not explain the outcome, error states, or whether a GUI app will be launched. Despite having an output schema, the description does not clarify return behavior, and without annotations, the tool's side effects remain opaque.

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 lists both parameters with brief explanations: 'path: Path to the file' and 'app_name: Optional application name to open with.' The schema itself has no property descriptions, so the description adds basic semantic value, but it lacks details like path format or app name resolution.

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 'Open a file with the default or specified application,' which specifies the action and resource. However, it does not explicitly differentiate from sibling tools like launch_app, though the file vs app distinction is implicit.

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 provides no guidance on when to use this tool versus alternatives. It only states what the tool does, with no mention of when to use it or when to use a different tool.

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