get_macro_series

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

No annotations are provided, so the description carries the burden of behavioral disclosure. It discloses that the response includes 1-, 3-, and 12-month changes, but it does not mention error handling, data source, or explicitly confirm read-only behavior (though the name 'get' implies it). This is minimal but not misleading.

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: two sentences plus a compact args block. It is front-loaded with the main purpose and includes only essential information without redundancy. Every sentence 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 one-parameter getter with an output schema, the description covers the essentials: what it does, parameter meaning, and how to discover keys. The phrase 'in detail' is slightly vague, but the output schema likely specifies the return structure. It is complete enough for a simple retrieval tool.

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 specifies 'key' as a string, but the description gives concrete examples ('treasury_10y', 'core_cpi', 'vix') and directs users to get_macro_snapshot to see all valid keys. This fully compensates for the 0% schema description coverage and makes the parameter semantics clear.

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 retrieves one macro series in detail, including 1-, 3-, and 12-month changes. This verb+resource structure distinguishes it from siblings like get_macro_snapshot, and the example keys (e.g., 'treasury_10y') add clarity.

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 implies when to use this tool (for a specific series) versus get_macro_snapshot (to see all series). It provides example keys and advises calling the sibling to discover available keys, but does not explicitly state exclusions or alternative conditions beyond that.

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