get_positioning_framework

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

No annotations are provided, so the description must convey behavioral traits. However, it only summarizes the framework content and does not disclose whether the tool is read-only, has side effects, or requires any prerequisites. It does not contradict annotations (since there are none), but it fails to provide meaningful behavioral transparency.

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 two sentences long, with no wasted words. The first sentence enumerates the framework's components compactly, and the second provides a strategic context. It is well-structured and easy to parse.

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 simplicity (zero parameters, no output schema), the description provides a thorough overview of the framework's contents, which is helpful for understanding what to expect. It does not explicitly state the return format, but for a content-delivery tool this is not a critical omission. The description is complete enough for the tool's complexity.

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?

The tool has zero parameters, so there is no parameter documentation burden. The baseline for 0-parameter tools is 4, and the description adds context about the output content, which is sufficient. No parameter semantics are needed.

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 resource: the positioning framework, listing its key components (WHO x OUTCOME x HOW x RECEIPT, four checks, anti-patterns, proof-inventory, moat check). While it lacks an explicit verb like 'retrieves' or 'returns,' the tool name plus the content summary make the purpose unambiguous. It distinguishes from sibling tools by focusing specifically on positioning.

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 statement 'Positioning is upstream of every other brand decision' implies that this tool should be used early, before other brand-related tools, but it does not explicitly name alternatives or define when not to use it. This gives a clear contextual hint but lacks concrete usage boundaries.

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