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

No annotations exist, so the description carries the full burden and it does not meet it. It does not disclose whether the tool returns a static prompt text, generates an analysis, or requires the optional query to be meaningful, nor does it mention determinism, side effects, or output shape. 'Save hours every week' is promotional rather than behavioral.

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?

Three short sentences, but the lead is a benefit claim ('Save hours every week') rather than the tool's function, so the definition is not front-loaded. All three sentences are marketing copy that could be trimmed without any loss of operational information.

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 one optional parameter, no output schema, and no annotations, the description must explain what the tool produces and how to use it; it does neither. The result is a blurb insufficient for an agent to call this tool with confidence, especially amid dozens of near-named roi-* siblings.

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 is a single optional 'query' parameter with 100% schema description coverage, so the schema already explains it. The description adds no meaning about how query scopes the playbook or what happens when it is omitted, which is the baseline expectation.

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 says it supplies a 'battle-tested prompt and operating playbook for restaurant/brand growth', which hints at a template/prompt resource with an ROI focus, but it never states a concrete verb-and-resource action or what the agent actually gets back. It also fails to distinguish itself from the many sibling ROI tools (roi-analyze-tool, roi-board-tool, roi-diag-tool, roi-formula-tool), so selection between them remains guesswork.

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 when-to-use, when-not-to-use, or alternative-tool guidance at all. The only context offered ('No setup, works in any LLM chatbot') describes deployment, not invocation conditions, leaving the agent with nothing to decide between this and the other roi-* siblings.

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