zhiqi_forum_boards

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

No annotations are provided, so the description carries full burden. It discloses that the tool lists public boards and that board codes are used for posting, which is useful, but it does not mention whether the tool is read-only (likely), whether authentication is needed, or what the return format is. More behavioral detail is needed for an unannotated tool.

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, compact sentence that is front-loaded with the purpose and a key usage note. It is appropriately sized and no words are wasted. Slightly more structure could be added, but it is efficient.

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 zero-parameter schema and no output schema, the description is relatively complete for a simple list operation. However, it does not mention whether the list is paginated, sorted, or if it includes any metadata. Since it's a listing tool, the agent might need to know if it returns all boards at once or requires pagination, which is missing.

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 0 parameters and schema coverage is 100% (empty schema). Since there are no parameters to document, the description inherently covers all parameter semantics. The description adds value by stating the purpose and the relevance of board codes for posting, so this is above baseline.

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 states the purpose: list public forum boards and notes the board code is used for posting. However, it does not differentiate from sibling tools like zhiqi_forum_post, zhiqi_forum_detail, or zhiqi_forum_search, and the verb '列出' (list) is generic without specifying the resource type beyond 'boards'.

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 minimal context – it implies this is a prerequisite for posting (since board codes are used for posting), but it does not explicitly say when to use this vs. other forum tools, nor does it mention any alternatives or exclusions. The agent must infer usage from the sibling list.

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