query_excel

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

With no annotations, the description fully carries behavioral burden. It discloses local filtering (no HTTP), implying read-only behavior. It does not mention auth or side effects, but these are not critical for a query tool. No contradictions.

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 a clear purpose sentence, followed by filter format block and Args list. It is reasonably concise, though the Args list could be slightly shorter.

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 output schema exists (true), the description does not need to cover return values. It adequately covers input parameters, filter syntax, and sorting/limiting. Missing details like pagination are minor.

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% but the description provides detailed parameter semantics: file_path source, filter format with examples, sort_by column names, descending default, limit default. This fully compensates for missing schema descriptions.

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 a stored Excel snapshot from scan_to_excel, with local filtering. The verb 'filter' and resource 'Excel snapshot' are specific, and it implicitly distinguishes from 'scan_to_excel' (scanning) and other get_* tools (online data).

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 links the tool to scan_to_excel output and mentions it's local and fast (no HTTP), giving clear context. However, it does not explicitly state when not to use it or list direct alternatives, leaving some implicit guidance.

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