series_info

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

With no annotations, the description carries the burden of disclosure. It states it loads and returns information, implying a read-only operation, but does not explicitly confirm it has no side effects or mention error handling. The return metadata list is useful but lacks depth about behavior edge cases.

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, with two main sentences plus a parameter definition. It is front-loaded with the core purpose and avoids extraneous details, though the parameter description could be integrated more cleanly.

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 tool with one parameter and a provided output schema, the description covers the input and the nature of the output (metadata list). It does not mention error scenarios or file prerequisites, but these are minor for an info retrieval 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?

Schema coverage is 0%, so the description must compensate. It explains 'inp_path' as 'path to the .inp file', which adds meaning beyond the schema's bare property name 'Inp Path'. This adequately clarifies the parameter.

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 the verb 'Load' and the resource '.inp file', and specifies that it returns basic information. While it doesn't explicitly name sibling tools, the focus on loading from a specific file type and returning metadata distinguishes it from generic load/preview tools.

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 implies usage for inspecting an .inp file's metadata, but does not provide explicit guidance on when to use it versus alternatives like load_data or preview_data. No exclusions or alternative tool references are given.

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