uae_source_records

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

The description adds context beyond the schema by noting records are 'live' and 'redacted,' implying freshness and potentially limited detail. However, it does not disclose whether the operation is read-only, requires authentication, or has rate limits. No annotations exist to fill these gaps.

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 a single, front-loaded sentence that efficiently conveys the core action without redundancy. Every word adds value.

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 three parameters and no schema descriptions, the description is insufficiently detailed. While an output schema exists, the lack of parameter semantics and behavioral context makes the tool definition incomplete for effective use.

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?

With 0% schema description coverage, the description must compensate but only mentions 'limit' in passing. It does not explain the purpose of source_id or query, leaving the agent uninformed about how to use these parameters correctly.

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 the tool fetches live, redacted, source-cited records from a source, using a specific verb and resource. However, it does not explicitly distinguish this from sibling tools like uae_source_get, though the implication is clear.

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?

No guidance is provided on when to use this tool versus alternatives, such as uae_source_get or uae_sources_list. The description only states the function without context for appropriate usage.

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