cn402_hanzi_pinyin

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

No annotations are provided, so the description carries the burden. It discloses pricing ('Price: unknown on Base') but fails to mention other behavioral traits like rate limits, authentication, or safety aspects. The description does not contradict any annotations since none exist.

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 contains a long list of redundant synonyms before the core sentence, making it wordy. The price information is useful but should be integrated concisely. Overall, it could be more streamlined.

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 tool with 2 parameters and no output schema, the description provides basic functionality and price context. However, it lacks details on output format, error handling, or character limit beyond schema, leaving some gaps in completeness.

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%, and the description adds little beyond the schema for the two parameters. The 'style' parameter is explained via keywords, but the schema already provides options. No additional semantic value is provided.

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 it converts Chinese characters to Pinyin with tone marks, and the tool name 'cn402_hanzi_pinyin' further clarifies the purpose. It distinguishes from sibling tools like stroke count or radical lookup, though the description is slightly redundant with multiple synonyms.

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 mentions 'For AI agents handling Chinese text-to-speech, Chinese language learning apps,' which gives context but lacks explicit when-to-use or when-not-to-use guidance compared to alternatives. No exclusions are stated.

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