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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It describes the conversion and styles but does not state whether the operation is read-only, has side effects, or any error behavior. For a transformation tool, safety profile is implicitly safe, but the description does not explicitly disclose it, resulting in a transparency gap.

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 extremely concise—two short sentences that are front-loaded with the core purpose and then clarify the 'text' parameter. Every word earns its place with no fluff or repetition.

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 bidirectional conversion tool with 2 parameters and no output schema, the description adequately conveys the inputs, output styles, and the fact that it returns pinyin. It does not mention edge cases or error conditions, but given the tool's simplicity and the absence of an output schema, it is reasonably 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?

Schema coverage is 0%, so the description must compensate. It provides meaning for 'text' ('Chinese text') and hints at style values via the output options ('with or without tones, first letters only, or slug'), but it does not specify exact accepted values or format for the 'style' parameter. Partial compensation, but leaves ambiguity.

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's purpose: 'Convert Chinese text to pinyin' with specific output options (tones, no tones, first letters, slug). This is a specific verb+resource and distinguishes it from sibling tools like bazi_chart or lunar_calendar which serve different functions.

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 the tool (whenever pinyin conversion is needed) and lists output styles, but it does not explicitly state when not to use it or mention alternatives. Since no sibling tool overlaps with pinyin conversion, the lack of exclusion is acceptable, but explicit usage guidance is missing.

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