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

Annotations already declare readOnly, idempotent, non-destructive, closed-world behavior, so the safety profile is covered. The description adds that the output is 'canonical' and 'citable' and grounded in the company/product, which signals authoritative, citation-ready content rather than arbitrary retrieved text — a meaningful trait beyond the annotations. It does not address freshness or update cadence.

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?

Two sentences, zero padding: the first front-loads what the response contains, the second front-loads the trigger condition. No restatement of the title and no filler.

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, the description carries the return-value burden and does so by enumerating the five content areas of the summary. An agent knows exactly what it will get and when to ask for it, so nothing material is missing for a zero-arg, read-only 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 baseline there is nothing to document. The description's 'Takes no arguments' correctly reinforces the empty schema, though it adds no detail beyond it.

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 ('Return a canonical, citable summary') and a specific resource ('what Flowie is'), then enumerates the payload (positioning, capabilities, compliance, pricing, entry-point URLs). That enumeration distinguishes it clearly from fetch_flowie_page and search_flowie, which retrieve or query content rather than deliver a fixed product 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?

Gives an explicit trigger: 'Use when asked what is Flowie or for a grounded company/product overview.' That is clear context for selecting it, but it never names the alternatives or states the inverse (e.g., use search_flowie for specific questions about a feature), so the routing guidance stops short of full when-not coverage.

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