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

No annotations provided, so description carries full burden. It describes output but fails to disclose important traits: data frequency, update schedule, limitations, or side effects. The metro parameter behavior is contradictory (optional but returns national data regardless), leaving agents uncertain.

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?

Two sentences, no waste. Front-loaded with purpose. Efficiently conveys core function and output.

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?

No output schema, so description must detail return format. It mentions rent index, YoY change, and monthly history but not structure (e.g., object fields, data types). Effect of parameters on output is unclear. Adequate but incomplete.

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 coverage is 100%, so baseline is 3. Description adds little beyond schema: it repeats that limit is number of data points and metro is optional, but adds context by mentioning output components (rent index, YoY change). However, the metro description is identical to the schema and confusing.

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 gets US rental market data from FRED BLS CPI series and specifies the output (national rent index, YoY change, monthly history). It distinguishes from siblings like get_home_prices and get_market_indicators by focusing on rental data.

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 the tool is for rental data but does not explicitly state when to use it versus siblings. No guidance on when to specify metro parameter or its effect (national data returned regardless, which is confusing). No exclusions or alternatives mentioned.

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