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

Beyond the readOnly/destructive annotations, the description discloses that strategy is dated judgement rather than measured evidence, that missing facts or strategy return null, and that it is free and never generates or revises a strategy. These are substantive behavioral caveats an agent needs before relying on the data.

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?

Content is front-loaded with the returned fields, followed by usage and caveats, with no filler sentences. It is dense but every sentence carries information; slight packing of the growth_strategy sub-fields is the only cost.

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?

With no output schema present, the description carries the burden of explaining return values, and it does so thoroughly by listing both the business fields and the growth_strategy sub-fields, plus null behavior. Nothing material for correct invocation is missing.

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 the baseline is 4. The description instead characterizes the returned payload (positioning, ICP, growth_strategy fields with version/source/date), which is useful but not parameter-related.

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?

States a specific verb (get) and resource (business context) and enumerates exactly what it returns: positioning, audience, ICP, pricing, features, competitors and growth_strategy fields. This is clearly distinguishable from siblings like get_competitors or get_voice_profile.

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?

"Read before planning or writing" gives a clear usage trigger, and "check it against current founder intent" frames how to treat the data. It does not name specific alternative tools or explicit when-not conditions, so it stops short of a 5.

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