marketing_get_brand_strategy

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

No annotations are provided, so the description must disclose behavioral traits. It fails to mention read-only status, required permissions, rate limits, or output nature. The description focuses solely on content, not on what happens when the tool is invoked.

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 sentence followed by a short directive, making it concise. It lists key frameworks efficiently. However, the list structure could be clearer for parsing, and the final phrase 'Use for the longer game' is somewhat ambiguous.

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 no parameters or output schema, the description partially fulfills completeness by explaining the tool's purpose. However, it lacks information about output format, usage frequency, or prerequisites, leaving gaps for effective agent selection.

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?

There are no parameters, so schema coverage is 100%. Baseline for zero parameters is 4, and the description adds no parameter info, which is acceptable. The description provides context about the tool's output content without needing to elaborate on parameters.

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 identifies the tool as providing 'evidence-based brand strategy' with specific frameworks (Byron Sharp, Binet & Field, category design). It distinguishes from siblings like positioning or messaging by focusing on long-term brand building. However, it could more explicitly state the action (e.g., 'returns a brand strategy brief').

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 hints at when to use ('Use for the longer game') but does not provide explicit guidance on when not to use or compare to sibling tools like positioning or messaging. It implies strategic rather than tactical use, but lacks clear boundaries.

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