get_model_files

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

Discloses that the tool is a read-only listing operation and clarifies that the directory is empty before the model is saved or run. With no annotations provided, the description carries the full burden and adds meaningful context about expected behavior.

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 front-loaded with the main purpose, then provides usage guidance, parameter details, and return value in a clear structure. While slightly verbose, every sentence adds value and earns its place.

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?

With one simple parameter and an output schema present, the description covers the key aspects: what it does, when to use, what files to expect, and the return format. It is complete enough for an agent to correctly invoke the tool.

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 only parameter 'model_id' is described in the tool description as 'Id of the model whose files to locate', adding semantic meaning beyond the input schema which only has a title. This helps an agent understand the parameter's role.

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 uses specific verb 'List' and resource 'on-disk files for a model', clearly distinguishing from siblings like 'get_results' and 'inspect_model' which deal with simulation data rather than file locations.

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 guidance on when to use: to locate input, output, and log files for opening. Also explains timing (files appear after save or run), offering context for usage. Does not explicitly state when not to use, but the context is clear.

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