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

With no annotations provided, the description carries the behavioral burden. It adds useful transparency by listing what the spec includes ('wedge, verbatim complaints, verified open-source accelerators, verification plan') and by noting output is formatted for a specific agent. It does not mention prerequisites, side effects, or whether any external data is fetched.

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?

Two tight sentences with no filler. The main purpose is front-loaded, and the second sentence efficiently enumerates the deliverable's key sections.

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 gives enough to understand the deliverable's substance and target format, but there is no output schema and no explanation of how parameters affect the generated brief, such as storefront's role or what happens when target is omitted. Sufficient for basic invocation, but gaps remain.

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 67%, and the description reinforces the 'target' parameter by naming its enum values '(codex, claude, or cursor)' and linking them to agent formatting. It adds little beyond the schema for app_id and storefront, which are already described.

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 verb and outcome: 'Produce a ready-to-build product specification for an opportunity' and lists the included components. However, it does not explicitly distinguish itself from the similarly named sibling get_opportunity_brief, so an agent must infer the difference.

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 implies when the tool should be used: when a ready-to-build specification for an opportunity is needed and a target AI coding agent is known. It does not explicitly state when not to use it or how it compares to siblings like get_opportunity_brief or find_unmet_demand.

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