mfuns_manage_submission

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

没有注释，描述承担行为透明责任。它说明了 update 不传 draft 会进入审核队列、草稿更新建议传 draft=true，以及 status 的数字含义，这些是重要的非显性行为。但未说明 delete 的不可逆性、权限要求或操作失败时的行为，覆盖不完整。

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?

描述采用分条 Args 格式，每行一个参数，信息密度高，先给出总体用途再列细节。虽然篇幅较长，但每个字段都有必要说明，没有冗余内容。

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?

作为多操作管理工具，描述覆盖了 list/update/delete 的参数要求、默认行为、状态过滤和更新审核行为，输出已有 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?

输入 schema 的 description 覆盖率为 0%，但描述对每个参数给出了含义、默认值、必填条件和可选范围，例如 action 的可选值、status 的枚举含义、draft 的行为影响，完全弥补了 schema 的缺失，甚至提供了超出 schema 的实际语义。

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?

描述明确指出'管理我的投稿'，并列出 list/update/delete 三种操作及类型参数，能区分于 mfuns_create_post 等兄弟工具。虽然未显式点名替代工具，但用途清晰，足以让智能体理解工具功能。

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?

描述详细说明了各操作的必要参数（update/delete 必填 contribute_id，update 必填 title/content/category_id），并给出 action 默认 list、size 上限等，使用场景清晰。但未提及与 mfuns_delete 或 mfuns_create_post 的明确分工，缺少排除性说明。

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