List Oracle open-data properties

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

With no annotations, the description carries the behavioral disclosure burden and does disclose pagination, slim vs summary field composition, and a conditional 'query table' behavior. However, it does not explicitly state read-only/side effects or clarify what 'served from the query table' means, leaving some behavioral ambiguity.

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 dense sentences with no filler. The action, scope, output highlights, and alternative tool are all front-loaded and each clause earns its place.

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 list tool with no output schema, the description provides enough return-field detail and pagination context to guide invocation. Minor gaps—the meaning of 'query table' and explicit confirmation of read-only behavior—prevent a perfect score.

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%, with defaults and constraints already documented for limit, county, and offset. The description adds contextual emphasis on county filtering and pagination but no new parameter-level meaning beyond the schema, so baseline 3 is appropriate.

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+resource scope: paginated discovery of properties for a county. It also names the output content and explicitly contrasts with getOracleProperty, making the tool readily distinguishable from its sibling get-tool.

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?

Clearly tells the agent to use getOracleProperty when full consolidated data for a specific entry is needed, which is an explicit routing instruction. It does not discuss broader listing/query siblings like queryProperties, but the primary alternative is well covered.

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