get_sources

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

With no annotations, the description must disclose side effects and return behavior; it only notes the optional file_path save behavior. It does not explain whether the sources are still returned when file_path is provided, nor any limits, pagination, or output structure.

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 concise with a clear lead sentence and an Args note. Every part earns its place and there is no repetition of the schema.

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 simple list-all tool with one optional parameter, the description covers the basics, but it lacks return-value details, usage context, and routing among the ten sibling tools. It is adequate but leaves meaningful gaps.

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?

The schema only says file_path is string|null with a default; the description adds that it is an absolute path used to save the sources list as JSON. This meaningfully clarifies the only parameter, though it does not describe behavior when omitted.

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 uses a specific verb, 'Get', and identifies the resource as 'all sources of economic data', making the tool's purpose clear. It does not explicitly distinguish from sibling get_source or search methods, but 'all sources' signals a bulk retrieval operation.

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 given on when to call this tool versus siblings like get_source or search_series, and no exclusions or prerequisites are stated. The agent must infer usage from the name and general context.

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