36ke_news

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

No annotations are provided, so the description carries full burden. '实时数据' implies real-time data fetching, but it doesn't disclose behavioral traits like rate limits, authentication needs, data freshness, or pagination. The description is too brief to provide meaningful context beyond the basic operation.

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 concise (two Chinese terms) but under-specified rather than efficiently informative. It front-loads the source name but lacks actionable details. While brief, it fails to earn its place by not clarifying the tool's purpose or usage.

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 complexity (a news fetching tool among many siblings), no annotations, and no output schema, the description is incomplete. It doesn't explain what data is returned (e.g., headlines, links, timestamps) or how it differs from other news tools. For effective agent use, more context is needed.

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?

With 0 parameters and 100% schema description coverage, the baseline is 4. The description doesn't need to explain parameters, and it doesn't add or contradict any parameter information. It appropriately avoids unnecessary details for a parameterless tool.

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 '实时数据/36氪热榜' is vague and tautological. It restates the tool name '36ke_news' in Chinese ('36氪热榜') and adds '实时数据' (real-time data), but doesn't specify what action the tool performs (e.g., fetch, list, retrieve). It doesn't distinguish from siblings like 'baidu_news' or 'zhihu_news' beyond the source name.

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 the 15 sibling news tools. The description doesn't indicate what makes '36氪热榜' unique (e.g., tech focus, trending topics) or suggest alternatives for different contexts. This leaves the agent with no basis for selection among similar tools.

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