mfuns_browse

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

The description discloses that 'latest' mode returns LLM-optimized Markdown from a third-party aggregator (mfuns.wgen.top), and that category_id is ignored in non-category modes. It does not explicitly state that the operation is read-only or mention auth/rate limits, but for a browse tool the read-only nature is implied and the markdown detail adds useful context.

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 compact and well-structured: a one-line summary followed by a clean Args list with each parameter on a separate line. Every sentence adds necessary information with no 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?

With 4 optional parameters and an output schema present, the description covers all parameter semantics, mode-specific behavior, and the special markdown format for latest mode. It lacks error handling details but that is not critical given the tool's simplicity and the presence of an output schema.

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 description explains every parameter in detail, including mode options with Chinese translations, category_id requirement and examples (51=交友专区, 49=站内互动), limit defaults/max, and content_type valid values for latest mode. This fully compensates for the schema's 0% description 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?

The description clearly states the tool's function: browsing Mfuns community content streams, and enumerates specific modes (recommend, hot, feed, category, latest). This distinguishes it from sibling tools like mfuns_read_thread (reading a single thread) or mfuns_search (searching).

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 mode-specific guidance (e.g., category_id required for mode=category) but does not explicitly state when to use this tool versus alternatives like mfuns_search or mfuns_read_thread. Usage is implied rather than explicitly contrasted with other tools.

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