impact_anchor_market

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

With no annotations provided, the description carries the full burden of disclosing behavior. It mentions the use of scoring and TAM/SAM/SOM framework, giving some insight into methodology, but it does not state whether the tool returns a recommendation, how inputs are processed, or any side effects. This is a significant gap for an analytical tool.

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, front-loaded sentence that captures the essential action and methodology with no wasted words. Every token contributes to understanding the tool's purpose.

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?

Despite having a rich schema with 5 parameters, the description lacks any mention of output format, likely return values, or how the scoring/TAM/SAM/SOM framework is applied. With no output schema and no annotations, the tool remains under-specified for an agent to fully anticipate execution results.

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 description does not add any parameter-specific meaning beyond what the schema already provides, but it does not need to since all parameters are documented. It neither enhances nor detracts from the schema's clarity.

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') with a clear resource ('beachhead market') and adds methodology ('scoring and TAM/SAM/SOM framework'). This clearly distinguishes it from sibling tools like 'impact_identify_champions' or 'impact_map_alternatives', which target different aspects of market strategy.

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 usage when one needs to choose a beachhead market, but it provides no explicit guidance on when to use this tool versus alternatives. There are no exclusions or references to sibling tools, so the context is clear but lacks explicit direction.

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