CSDN

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

No annotations exist, so the description must reveal behavioral details. It only states the tool 'gets' data, but omits side effects (e.g., caching, rate limits), the effect of the 'noCache' parameter, and whether results are paginated. This lack of disclosure hinders correct invocation.

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 a single sentence, which is concise but at the expense of essential details. It front-loads the purpose but fails to include parameter explanations or usage context, leading to under-specification.

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?

Given the absence of annotations, output schema, and descriptive parameter information, the description is grossly incomplete. It does not address common concerns like return format, error handling, or how to interpret results, making it insufficient for reliable use.

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 description coverage is 0%, and the description does not explain the 'limit' or 'noCache' parameters. Without any context, agents have no information about what these parameters control or valid values, making correct usage unlikely.

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 '获取CSDN热榜数据' (Get CSDN hot list data), specifying the resource (CSDN hot list) and action (get). The title 'CSDN' further disambiguates from sibling tools targeting other platforms. However, it lacks specificity about what the hot list contains (e.g., articles, discussions), leaving some 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 is provided on when to use this tool vs. alternatives. With numerous sibling tools for different platforms, explicit directions on when CSDN is appropriate are missing, forcing agents to infer based solely on the platform name.

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