get_shelf

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

With no annotations, the description carries the behavioral burden. '书架列表' strongly suggests a read-only list operation and '官方通道' hints at the data source, but the description does not disclose authentication requirements, scoping to the current user, or error/pagination behavior. This is acceptable for a simple getter but not fully transparent.

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 very short and front-loads the core term, which is concise. However, '官方通道' is an unexplained parenthetical that may add confusion rather than clarity, and the description is a fragment rather than a well-structured sentence.

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 zero-parameter tool with an output schema, the core purpose is mostly covered. Still, the description omits context about whose bookshelf is returned, whether authentication is needed, and what 'official channel' means relative to the sibling tools, leaving the agent to infer these details.

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 input schema has zero properties, so there are no parameter semantics to document. The description reinforces that the tool simply returns a bookshelf list without arguments, satisfying the baseline for a no-parameter tool.

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 resource ('书架列表' = bookshelf list) and clearly implies the operation of listing it, matching the tool name get_shelf. It is distinguishable from siblings like get_toc and get_progress because it uniquely targets the bookshelf. The '官方通道' qualifier adds a channel context but is not needed to understand the core purpose.

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 implies the tool should be used when an agent needs a bookshelf list, and no sibling tool appears to provide the same function. However, it gives no explicit when-to-use guidance, exclusions, or alternatives, and the meaning of 'official channel' is not explained.

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