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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, and openWorldHint, so the safety profile is fully covered by structured data. The description adds the meaningful behavioral context that this is a compound read operation supporting filtering, aggregation, sorting, and pagination, but says nothing about result caps, error behavior, or dataset-scope limits beyond the annotations.

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 tight sentences with no filler, and the core purpose is front-loaded ahead of the operation summary. The minor grammar slip ('a ODRE') is cosmetic and doesn't impede parsing.

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 8 fully documented parameters and no output schema, the main remaining gap is guidance on how this differs from sibling query tools (search_datasets, search_within) and whether a dataset_id must first be obtained elsewhere. Adequate but incomplete for a primary query 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?

Schema description coverage is 100%, so the schema fully documents all 8 parameters, and the baseline is 3. The description adds marginal value by grouping parameters under their operations (where=filter, group_by/select=aggregate, order_by=sort, limit/offset=paginate), but the mapping is already evident from the schema.

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 (Query) and resource (records from an ODRE Energy Open Data dataset) plus the query language (ODSQL), so the agent knows exactly what the tool retrieves. It doesn't explicitly distinguish itself from siblings like search_datasets, dataset_info, or search_within, which keeps it from a 5.

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 description enumerates the supported operations (filter, aggregate, sort, paginate), which implies when the tool is useful, but it never states when to use it versus search_datasets or dataset_info, nor any prerequisites such as needing a dataset_id first. Usage is implied rather than prescribed.

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