native_api_operation

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

With no annotations provided, the description carries the full burden. It does disclose that operations are authenticated and allow-listed, which are safety-relevant constraints, but it doesn't mention side effects, error behavior, or whether operations can be destructive. For a generic operation invoker, this is insufficient.

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 a single, information-dense sentence with no redundancy. It front-loads the core purpose and adds a useful constraint about not being an HTTP proxy. Every clause earns its place.

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?

Although an output schema exists (so return values are covered), the description still lacks context for how to formulate operations, what parameters mean, and what constitutes an allow-listed operation. For a tool with four parameters and no schema descriptions, this is a significant gap.

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 description coverage is 0% and the description does not explain any of the four parameters. 'operation' is implicitly required, but payload, task_id, and artifact_id remain completely unexplained. The description adds no meaning beyond the bare parameter names.

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's function: calling an authenticated, allow-listed native-server operation, using a specific verb and resource. It also distinguishes itself from arbitrary HTTP proxying, which sets it apart from a generic proxy tool. However, it doesn't enumerate available native operations, so the scope remains somewhat open.

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 gives a negative usage guideline ('never an arbitrary HTTP proxy') but does not provide positive guidance on when to choose this tool over siblings like execute_js or crawl_stream. The context is implied: use it for authenticated, allow-listed operations, but there's no explicit when-to-use or alternative comparison.

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