powerquery

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

With no annotations, the description covers behavioral cues: it executes queries (read operation implied), timeout handling, empty result handling. It doesn't explicitly state it's non-destructive but is clear from context. Could add that it does not modify data.

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 relatively long but well-structured with sections for purpose, usage guidelines, time range, and understanding results. It front-loads key info. Could be more concise but remains effective.

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 complexity of a PowerQuery tool with 3 params and output schema, the description adequately covers tool purpose, how to generate queries, time handling, and result interpretation. It doesn't detail the output schema but that is covered by schema. Missing explicit parameter format, but overall complete enough for correct use.

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 description mentions query is a PowerQuery string and time range parameters, referencing get_timestamp_range. However, it does not specify datetime format or describe the output schema. The description provides context but lacks detailed parameter semantics.

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 tool executes PowerQuery analytics on SentinelOne's Singularity Data Lake for threat hunting. It distinguishes itself by noting it is not Microsoft PowerQuery nor Splunk SPL, and it's the only tool that runs PowerQuery queries among siblings.

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: use purple_ai() to generate queries, don't modify user-supplied queries, default time range to 24 hours, timeout of 5 minutes, and acceptable empty results. It tells when to retry and when not to.

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