shibor_lpr

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

With no annotations, the description must fully disclose behavior. It lists parameters and fields but does not explain default behavior when no dates are given, update frequency, data sources, or error handling. This is minimal transparency.

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 well-structured with sections for Name, Description, Args, and Fields. It is reasonably concise, though some repetition of 'LPR贷款基础利率' could be trimmed.

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 Fields section implies return values (date, 1y, 5y), but it lacks details on default date range, rate precision, or data availability. For a simple lookup tool, it is adequate but not fully complete.

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?

Despite 0% schema coverage, the description includes a table explaining each parameter: start_date and end_date must be used together, fields selects from the listed options. This adds meaningful context beyond the schema.

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 that the tool retrieves LPR (Loan Prime Rate) rates. It explains what LPR is, distinguishing it from sibling tools like cn_cpi or cn_gdp, but does not explicitly clarify that it returns historical time series.

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 like other financial indicators. It lacks conditions, prerequisites, or situational recommendations.

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