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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is covered structurally. The description adds that the call is 'Free' and that the cap is provider-enforced with no fake scarcity, which is useful context, but it doesn't explain return format or how the listed data is delivered.

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?

Everything is packed into one long run-on sentence with nested parentheticals (stage, offer, live), making it dense and hard to parse. The opening phrase is front-loaded but the parenthetical stacking hurts readability.

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?

There is no output schema, so the description carries the burden of explaining what the agent gets back. It enumerates the subject matter well but never clarifies the returned structure or how the founder stage/offer/live states map to output, leaving a gap for a zero-param read tool.

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 takes zero parameters, so per the rubric this sits at the baseline of 4. The description lists conceptual 'inputs' (stage, signups, payments, offer, live) but these are not real parameters, so there is little parameter semantics to add or omit.

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 frames the tool as reference material ('What a founding offer starts from') and enumerates the data it covers (founder stage, signups/payments, existing offer, live offer), but never states a clear verb+resource action—it reads more like a topic outline than 'this tool returns/does X'. An agent can guess it surfaces founding-offer context, but the actual operation is vague.

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?

There is no explicit when-to-use or when-not-to-use guidance. The only routing hint is an oblique 'live: what a boost leads with', which gestures at boost_plan but does not name it or state the condition for choosing this tool over that sibling.

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