forward_submit_brief

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

No annotations exist, so the description must carry the behavioral burden. It briefly notes the return value (brief_id + missing fields) but does not disclose side effects such as resource creation, cost implications, or authentication needs. The verb 'submit' implies mutation, but this is not explicitly stated.

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 very short (one sentence) but this brevity comes at the cost of clarity. It is underspecified rather than concise, missing critical information that would help an agent use the tool effectively.

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 tool has 6 parameters (4 required), nested objects, no annotations, and no output schema, the description is severely incomplete. It fails to provide essential context about the tool's operation, parameter semantics, or expected behavior.

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 parameter meaning. With 6 parameters including required fields like icp, volume, and budget_cap_usd, the agent receives no guidance on what these mean or how to provide valid values.

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 states 'Describe who you want as customers' and mentions returning a brief_id, which hints at creating a customer brief. However, it lacks specificity about what the tool actually does (submits a brief for processing), and doesn't differentiate from sibling tools like forward_quote or forward_checkout.

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?

No guidance is provided on when to use this tool versus alternatives. There is no context about prerequisites, when not to use it, or how it compares to forward_quote, forward_checkout, etc.

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