coolapk_topic

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

No annotations are provided, so the description carries the burden. It does add genuine behavioral context by explaining the hot_first scoring formula (likes + comments*3) and that disabling it yields Coolapk's default time-ordered, low-engagement flow. It does not state that this is a read operation or mention rate limits/pagination behavior.

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?

Front-loaded one-line purpose followed by a compact per-parameter list. Every line earns its place, though the Args block largely mirrors schema property names and defaults are implied rather than restated.

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?

An output schema exists, so return values needn't be explained. However, with no annotations and no statement of read-only safety or pagination behavior (e.g. what happens past the last page), the definition leaves some behavioral gaps for a browse tool.

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%, so the description must compensate, and it does: tag, with_feeds, page, and hot_first are all explained, with hot_first given rich semantics beyond its name. The tag description ('话题标签名') is somewhat terse but sufficient.

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?

States a specific verb and resource: view Coolapk topic details or the feeds within a topic. This is clearly distinct from search/feed_detail siblings, though it doesn't explicitly name those alternatives. Slight ambiguity remains about whether 'details' and 'feeds' are one call or two modes.

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 with_feeds flag implies when feed listing is returned, and hot_first implies sorting choice, but there is no explicit guidance on when to choose this tool over coolapk_search or coolapk_feed_detail, nor prerequisites. Usage is inferable rather than stated.

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