uae_source_records

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

With no annotations, the description carries full responsibility for behavioral disclosure. It states records are 'live, redacted' and that responses include 'provenance + a data-quality block in `meta`.' This indicates read-only behavior and some response structure. However, it does not mention authentication, rate limits, error handling, or side effects.

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 description is three sentences, each serving a distinct purpose: core action, dataset parameter use, and response content note. No redundant or irrelevant information. Front-loaded with the main action.

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?

Given the tool has 5 parameters and an output schema, the description covers the essential purpose and the key parameter (dataset). It also notes the presence of provenance and data quality in responses. However, it could elaborate on the query parameter's semantics or pagination behavior.

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 0%, so the description must add meaning. It explains `limit` (default 10) and `dataset` (an id from uae_source_datasets). It also implies `offset` and `query` are available but does not describe them. This adds value over the bare schema, but not all parameters are explained.

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 clearly states 'Fetch up to `limit` live, redacted, source-cited records from a source.' This specifies the verb (fetch), resource (source-cited records), and constraints (live, redacted, limit). It also mentions multi-dataset portals. However, it does not explicitly differentiate from sibling tools like uae_search or uae_source_aggregate.

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 provides guidance on when to use the `dataset` parameter: 'For multi-dataset portals pass `dataset` (an id from `uae_source_datasets`).' This implies that for single-dataset sources, dataset is not needed. However, it does not specify when to use this tool over alternatives like uae_search for cross-source queries or uae_source_get for a single record.

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