ai_execute_goal

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

The description mentions that the agent runs a loop and returns a step log, but it does not state whether the agent can perform side effects or take destructive actions. With no annotations, the full burden is on the description, which lacks explicit safety details.

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 two sentences, compact and well-structured. It states the primary function, notes dependencies, and gives usage preference, all without redundancy.

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?

The description provides sufficient context by directing users to prefer primitive tools and clarifying when delegation is appropriate. It also notes the external dependency on API keys, making the overall context complete.

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?

The 'goal' parameter is explained implicitly as 'natural-language goal', but 'max_steps' is not described in the text or schema. Since schema coverage is 50% (one of two parameters explained), the description adds moderate value but leaves a gap.

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 that the tool delegates a natural-language goal to a server-side AI agent that runs an observe-think-act loop and returns a step log. The purpose is unambiguous and specific.

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 explicitly says to prefer primitive tools unless the user explicitly asks to delegate, providing a clear when-to-use guideline. It also mentions the required API keys, which is a practical usage condition.

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