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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and closed-world, so safety behavior is covered. The description adds a genuinely useful scope caveat (information only; FlowFresh does not broker fruit), which helps an agent avoid misusing it as a commercial contact. It does not disclose what the tool actually returns or how the contact route is presented, so the added value is moderate.

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?

A single front-loaded sentence with no filler. The parenthetical caveat earns its place by constraining the tool's purpose.

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 parameters and no output schema, the description carries the burden of explaining what the agent gets back, and it stops short of saying so—there is no indication of whether it returns an address, email, phone number, or form. For a simple static lookup this is adequate but leaves a real gap in what to expect from the call.

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 there is nothing for the description to disambiguate; the baseline of 4 applies. No parameter omissions or misrepresentations are present.

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 clear purpose: it is a contact route for enquiries about the reference data, i.e. how to reach FlowFresh. The verb is slightly indirect ('How to reach...') rather than a crisp 'Returns contact details', but the resource and intent are unambiguous. It does not explicitly distinguish itself from siblings like get_specs or list_products, though the contact/information framing implicitly separates it.

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 gathers that this tool is for reaching FlowFresh rather than retrieving product or season data. The disclaimer 'FlowFresh does not buy, sell or broker fruit' usefully scopes the kind of enquiry that is appropriate. There is no explicit when-to-use vs alternatives statement or prerequisite guidance.

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