rwa_bond

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

No annotations provided. The description mentions cost and free tier, which is helpful but does not disclose query behavior, response format, or any side effects. Significant gaps remain.

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 short but wastes precious space on pricing and API URL without clarifying core purpose. It is not front-loaded and misses essential operational details.

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 single-parameter tool in a complex domain (RWA bonds), the description lacks crucial context: what bond data is returned, expected query format, and output structure. Incomplete for effective agent invocation.

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 has 100% coverage with one parameter 'query' described as '查询条件'. The description adds no further meaning beyond the schema, so baseline of 3 applies.

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 indicates it provides RWA bond data ('RWA债券数据'), but lacks a specific verb like 'get' or 'fetch'. It is clear enough about the resource but not the action, leaving ambiguity.

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 on when to use this tool versus sibling RWA tools (e.g., rwa_commodity, rwa_credit). The pricing info hints at use, but no contextual differentiation or prerequisites.

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