site_content

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

No annotations are provided, so the description carries the full behavioral burden, and it discloses almost nothing beyond the bare action. It doesn't say whether this is read-only, how deep the channel/entry traversal goes, whether entries are paginated or truncated, or what permission or key validity requirements exist. '取' implies a read, but nothing is confirmed.

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?

A single short sentence with the action front-loaded and no filler. It is efficient, though its brevity contributes to the ambiguity noted in other dimensions.

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?

For a simple one-parameter read tool with full schema coverage and no output schema, the description is minimally viable. However, with no annotations and no mention of the sibling it complements (sites_index) or differs from (site_detail, site_search), an agent lacks enough context to pick it confidently in a large toolset.

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?

There is a single required parameter with 100% schema description coverage, so the schema already explains that key is a site key found via sites_index. The description adds no further meaning about the key's format or behavior, so the baseline of 3 applies.

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 names a specific verb (取, fetch) and resource (a site's 栏目 channels and 条目 entries, with examples like 通知公告 / 新闻 / 答辩公告). An agent can tell this returns site content rather than a site list or a search, though it never contrasts itself with site_detail or site_search.

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?

There is no explicit when-to-use guidance and no alternatives named. The only hint is the schema text pointing at sites_index for the key, which is in structured data, not the description. An agent must guess how this differs from site_detail or site_search.

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