query_excel

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

The description discloses that it is fast due to local filtering without HTTP calls, and supports multiple queries on the same file. No annotations provided, so this is adequate but does not address error handling or side effects.

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 a clear structure: general description, usage context, filter examples, and parameter list. It is efficient and well-organized.

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 the 0% schema coverage, the description compensates well by explaining filter formats, output format (markdown table), and the file source. Missing details like column names are acceptable for this simple query 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?

With schema coverage at 0%, the description explains the filter format with examples and lists each parameter with its role and default values, adding significant value beyond the bare schema.

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 it queries an Excel snapshot for filtering stocks, and specifies it is for files created by scan_to_excel. It distinguishes from siblings by indicating it works with local files, but does not explicitly contrast with other 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 mentions when to use (for files from scan_to_excel) and that multiple conditions can be queried on the same file, but lacks explicit when-not-to-use or alternative tools guidance.

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