Get a FRED source

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the read-only nature is established. The description adds an example call and the scoping by source_id, which is useful but does not disclose any additional behavioral traits such as error handling, rate limits, or the structure of the returned metadata.

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 very concise with two sentences and a practical example. It is front-loaded with the core purpose and provides an illustrative call, wasting no words.

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?

The tool is simple and the output schema covers return values, but the description leaves the optional realtime parameters unexplained. Given the low parameter coverage and lack of usage guidance, the description is adequate but not fully complete for an agent to confidently invoke with correct optional parameters.

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 explain the parameters. It explains source_id via the example and 'by source ID', but realtime_start and realtime_end are not mentioned or described, leaving their meaning and usage ambiguous despite having defaults.

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 'Get metadata for a FRED source by source ID', which specifies a verb, resource, and key parameter. It does not explicitly differentiate from sibling tools like list_sources or get_source_releases, but the singular 'a FRED source' and 'by source ID' make the purpose clear enough.

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?

There is no guidance on when to use this tool versus alternatives such as list_sources or get_source_releases. The example demonstrates invocation syntax but provides no context about appropriate use cases or criteria for selecting this tool over others.

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