豆瓣小组

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

No annotations provided, and the short description fails to disclose any behavioral traits such as read-only nature, authentication needs, rate limits, or side effects. The agent cannot infer safety or usage constraints.

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?

Extremely concise (one short sentence), but under-specification sacrifices clarity. While word count is low, the description lacks necessary structure and detail.

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 no annotations, no output schema, and 0% schema coverage, the description is woefully incomplete. It does not explain what the tool returns, how to use parameters, or any behavioral context.

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 mention or explain any parameters ('limit', 'noCache'). The agent gets no additional meaning beyond what the schema names imply.

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 '获取豆瓣小组精选' vaguely indicates fetching selected content from Douban groups, but it does not specify what is returned (e.g., posts, groups, topics). It distinguishes from siblings like 'douban-movie' but lacks precision.

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 on when to use this tool vs alternatives. With many sibling tools for different platforms, the description provides no context for selection.

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