impact_anchor_market

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

No annotations are provided, so the description carries the full burden. It only states that the tool 'selects' a market category and strategy, but does not disclose whether it reads inputs to produce a recommendation, mutates any state, or has side effects. The behavior is entirely opaque.

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, efficient sentence that is front-loaded with the verb and key objects. It avoids redundancy and is easy to parse, though it may be too brief to be fully useful.

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's complexity (5 parameters, no output schema, no annotations), the description is inadequate. It does not explain what the tool returns, what 'A phase' means, or how it fits into the broader impact_ process, leaving a significant gap in understanding.

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 100%, so the baseline is 3. The tool description adds no additional meaning about how the parameters (e.g., `product_description`, `current_category`) influence the selection of market category or beachhead strategy, but the schema already documents each parameter.

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 uses a specific verb ('Select') and names the resources ('optimal market category' and 'beachhead strategy'), with an added phase qualifier ('(A phase)'). This clearly communicates the tool's function and distinguishes it from sibling tools like `impact_get_framework` or `impact_craft_message`.

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 provides no guidance on when to use this tool versus the sibling tools, no exclusions, and no prerequisites. It simply states the action without any contextual 'when to use' information.

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