get_media_info

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

With no annotations, the description carries full disclosure burden. It transparently explains the distinct behaviors for different media types: returns URL for WeChat/articles/web/files, and auto-pulls plain text note_content for note_ prefixed IDs. It lacks error-case or permission details, but provides essential behavioral expectations.

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?

Description is concise, front-loaded with purpose, then provides source and type-dependent behavior in logical order. Every sentence earns its place with no redundancy or fluff.

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 single-parameter tool with no output schema and no annotations, the description is complete: it covers what it does, where the input comes from, and what output to expect for all mentioned cases. It fully enables an agent to select and invoke the tool correctly.

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 only says media_id is a media entry ID. Description adds meaningful context: the ID comes from specific source tools and that note_ prefix triggers different behavior. This enriches parameter understanding beyond the schema, justifying a higher score despite high schema coverage.

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?

Description clearly states the tool gets original content or download link for a knowledge base entry, using a specific verb and resource. It distinguishes from sibling tools by detailing type-dependent behavior (URL for articles/web pages/files, note_content for notes), making its unique function explicit.

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?

Explicitly instructs to pass media_id from the return of get_knowledge_list or search_knowledge, providing clear context on when to use this tool. However, it does not explicitly state when not to use it or mention alternatives like get_note_content, though the description implicitly covers note handling within this tool.

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