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

Annotations already establish readOnly, idempotent, non-destructive, closed-world behavior, so the safety profile is covered. The description adds genuinely non-obvious context beyond that: the data is 'generated from the code that charges it' and 'safe to cache', which tells the agent about authority and staleness — a meaningful freshness guarantee an agent could not get from annotations. It stops short of describing the response shape or field names.

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?

Front-loaded with the core statement, then detail clauses, then the caching note last — a sensible ordering. It is a single long semicolon-chained sentence, which is dense but each clause carries a distinct pricing fact (free tier, no trial, bps fee, processor fee separate, cash free), so little could be cut without losing substance. Slightly heavier than ideal for skim-reading.

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?

For a zero-parameter, read-only lookup with no output schema, the description does the schema's job by enumerating the facts returned, including the bps unit of the platform fee and the separation of the processor's fee. An agent can answer a pricing question from the description alone and knows the data is cacheable.

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 the baseline is 4; there is nothing for the description to disambiguate. It correctly avoids inventing parameter talk and spends its words on payload content instead.

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 opens with a specific verb and resource ('Return Thmenu's commercial model as structured facts') and then enumerates the exact facts returned: free forever, all features included, no subscription, no trial, a bps platform fee on processed payment volume, and no Thmenu fee on cash/external payments. This clearly separates it from siblings like get_faq or sales_summary, which could superficially seem related to pricing questions.

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?

Usage is only implied: an agent can infer this is the tool for 'what does Thmenu cost / what are the fees' questions. There is no explicit when-to-use statement, no exclusion, and no pointer to alternatives such as get_faq, which might also answer commercial questions. Adequate but leaves routing to inference.

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