get_batch_notes_from_favorites

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

With no annotations, the description carries the burden. It discloses automatic calls to sibling tools and that all URLs include xsec_token. It does not mention failure handling, rate limits, or that it is a read-only operation, but the provided context adds meaningful value beyond what schema gives.

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?

Three sentences, front-loaded with the main purpose, followed by the internal mechanism and a usage note. Every sentence earns its place; no redundancy or filler.

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 composite tool with 2 params and no output schema, the description explains its internal calls and token handling, which is essential. It lacks detail on result structure or partial failure behavior, but overall it is reasonably complete given the tool's complexity.

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 covers both parameters with descriptions (100% coverage), so the description adds little new param info. The note about avoiding timeouts is already in the schema's limit description. The description's mention of xsec_token is behavioral, not param-specific.

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 clearly states the tool batches full note content (text and images) from the current user's favorites. It distinguishes itself from sibling tools by explicitly mentioning it internally calls get_favorites_list and get_note_content, making its composite nature obvious.

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?

Provides a clear use case ('适用于批量分析收藏的笔记') and explicitly describes the internal workflow. It does not explicitly state when NOT to use it or how it compares to using the sibling tools directly, but the context is sufficient for most agents.

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