inspect_data

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

No annotations provided, so description carries full burden. It describes a read-only inspection returning metadata, with no indication of side effects. The listed return items (bounds, arrays, timestep, multiblock) provide behavioral transparency beyond the schema.

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?

Two concise sentences: first defines action and output, second provides usage guidance. No wasted words, front-loaded with key information.

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, presence of output schema (though not detailed), and usage advice, the description is largely complete. Minor gaps: no mention of file format restrictions or glob behavior, but acceptable for a simple inspection 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?

Only one parameter (file_path) with 100% schema coverage. The description adds usage context ('Inspect a simulation file') and the schema provides example paths. No extra semantic detail needed, but the description reinforces 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 clearly states 'Inspect a simulation file and return metadata' and lists specific return types (bounds, arrays, timestep, multiblock). It distinguishes from siblings by positioning as the first step before rendering or extracting, aligning with its name.

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 this first to understand what data is available before rendering or extracting,' providing clear context for when to invoke. Lacks explicit when-not-to-use or alternatives, but the sibling tool list implies specialized tools for later steps.

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