实时数据/虎扑步行街热榜

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

With no annotations provided, the description carries the full burden of behavioral disclosure but offers none. It doesn't indicate whether this is a read-only operation, if it requires authentication, what rate limits apply, or what the output format might be. The description is purely a label with no behavioral context, making it inadequate for a tool that presumably fetches real-time data.

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 phrase that mirrors the tool name, making it overly concise to the point of under-specification. It lacks structure (e.g., no verb or operational details) and doesn't front-load critical information. While brief, it fails to convey useful content, so it doesn't earn a high score for conciseness.

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 of real-time data fetching and the lack of annotations or output schema, the description is severely incomplete. It doesn't explain what the tool returns, how to interpret results, or any operational constraints. For a tool with no structured metadata, the description should provide essential context but does not, leaving the agent with minimal actionable information.

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?

The tool has zero parameters, and the input schema has 100% description coverage (though empty). The description doesn't need to compensate for missing parameter documentation, so it meets the baseline. However, it doesn't add any semantic context about parameters since there are none, which is acceptable but not exceptional.

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?

Tautological: description restates name/title.

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 provides no guidance on when to use this tool versus alternatives. There is no mention of context, prerequisites, or differences from sibling tools like '虎扑步行街热榜A' or other real-time data tools (e.g., '微博热搜', '知乎热榜'). This leaves the agent with no information to make an informed 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.