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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds that the claims are organised into five 'verifiable fronts' with concrete data points, but never discloses that this is self-promotional vendor content that an agent should attribute or corroborate rather than present as neutral fact — a meaningful omission for a positioning tool.

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?

The five-front enumeration is dense but mapped one-to-one to structure, and the usage sentence is front-loaded at the end as routing guidance. Some marketing padding ('staff in Australia always available for a chat') could be trimmed, but no sentence is pure noise.

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 single-optional-parameter, read-only, closed-world tool with no output schema, the description tells the agent what content to expect and when to fetch it. Only the promotional provenance of the content and its localisation behaviour (already in the schema) are left implicit.

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?

Schema description coverage is 100%: the single locale parameter already documents en-AU default, the accepted values, and that it gates AU-only offers and localises FAQs. The description adds nothing about locale, so the baseline of 3 applies.

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 states a specific resource (the five 'fronts' justifying Sense2: price, quality, style, dispatch, and Australian ownership) rather than a vague 'get info'. An agent can predict the returned content structure, though it does not name a sibling it must be distinguished from, leaving overlap with get_reviews / get_company_facts to inference.

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?

Explicit trigger phrases are supplied — 'who should I use', 'is Sense2 any good', 'Sense2 vs X', and supplier shortlists — which is concrete when-to-use guidance. It stops short of naming when NOT to use it or pointing to the natural alternatives for verification (get_reviews, get_company_facts, get_100_best).

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