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

With no annotations, the description carries the full burden, and it does disclose two useful traits: answers are grounded with cited web sources, and a SuperhotGeo API key is required. It says nothing about rate limits, cost, latency, answer length, or what happens on an out-of-domain or key-less call.

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 dense paragraph that front-loads the verb and domain, then the return format, then the auth prerequisite. Every clause earns its place; nothing is repeated from the schema.

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 one-parameter question-answering tool with no output schema, the description covers what it does, what comes back (grounded answer with citations), and the API-key requirement. Only operational details like failure modes and limits are absent, which is a minor gap at this complexity.

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 coverage is 100% and the single parameter is fully documented, so the baseline applies. The description does implicitly constrain the question to the geothermal domain, which is meaningful, but it adds no format, length, or phrasing guidance beyond the schema's maxLength.

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?

Specific verb ("Ask") plus a named resource ("SuperhotGeo Assistant") and an enumerated domain scope covering science, technology, projects, economics, policy, companies, and the platform itself. The web-grounded answer with cited sources also distinguishes it from data-lookup siblings like search_wells or search_library.

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?

The domain scope plus "returns a grounded answer with cited web sources" gives clear context for when this is the right call versus the search-oriented siblings. However, no sibling is named and there are no explicit exclusions (e.g., "do not use for well-level data, use search_wells"), leaving the routing inference to the agent.

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