raw_api_query

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

No annotations provided. Description states GET query (read-only), but does not disclose potential impacts like large data returns, rate limits, or permission requirements. Minimal behavioral disclosure beyond the HTTP method.

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?

Single sentence, no redundant information. Efficient, but could be slightly expanded to include output format or safety warnings without losing conciseness.

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?

No output schema exists, yet description gives no hint about the return format (e.g., XML). For a raw query tool, this is a significant gap. Also lacks advanced usage notes or error handling context.

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 100% with clear parameter descriptions for entity, filter_key, filter_criteria (including examples). The tool description adds no extra meaning, so baseline of 3 is appropriate.

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?

Description clearly states 'Execute a raw API GET query for any entity', with specific verb and resource. It distinguishes from sibling tools like list_firewall_rules, get_time_settings which are entity-specific, by emphasizing 'any entity' and 'advanced usage'.

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?

Only mentions '(advanced usage)' which implies caution but does not specify when to use this tool versus the many dedicated list/get tools. No explicit when/when-not advice or alternative tool references.

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