get_competitive_positioning

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

Annotations already declare readOnlyHint=true and openWorldHint=true, indicating safe read operations with open-ended inputs. The description adds valuable behavioral context by specifying the battlecard's components (where you win, attack points, questions to plant, landmines), which goes beyond what annotations provide about operational safety.

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 front-loads the core purpose and immediately details the battlecard's four key components. Every element serves a clear purpose with zero wasted words.

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?

For a read-only tool with rich annotations and comprehensive schema documentation, the description provides good contextual completeness. The battlecard metaphor effectively conveys the output's structure and utility, though without an output schema, some details about return format remain unspecified.

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?

With 100% schema description coverage, all parameters are well-documented in the schema. The description doesn't add parameter-specific semantics beyond the battlecard metaphor, but the schema provides comprehensive parameter descriptions including inference guidance for productDescription, vertical, and targetRole.

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 tool's purpose with specific verbs ('gives you the battlecard') and resource ('for a specific competitor'), and distinguishes it from siblings by focusing on competitive positioning analysis rather than other sales/marketing functions like prospect discovery or account planning.

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 context through the battlecard metaphor (sales/marketing scenarios), but doesn't explicitly state when to use this tool versus alternatives like 'get_capability_profile' or 'get_messaging_framework'. No explicit exclusions or prerequisites are mentioned.

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