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

注解已声明 idempotentHint=true 与 destructiveHint=false，安全画像已有覆盖。描述额外补充了重要行为：一人一家（唯一性约束）、立即公开、触发异步处理，以及 slug_taken 时换 slug 的错误恢复策略，这些确实超出注解范围。但未说明异步处理的产物是什么、公开是否可撤回。

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?

两句话，先写登录与确认前提，再写唯一性/公开/异步等关键行为，最后用箭头链路收尾，信息前置且紧凑。箭头链式写法略带电报体风格，但无冗余句子。

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?

对一次 9 参数、会异步触发公开状态变更的写操作而言，描述覆盖了前置条件、唯一性、错误恢复和后续步骤，但未提及异步完成后如何查询结果（如 get_my_company / get_onboarding_status 之外的确认方式），也无输出 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 描述覆盖率已达 100%，9 个参数中 8 个为可选且均有中文说明，基线即为 3。描述仅额外点明 slug 冲突的处理方式（slug_taken 换 slug），对必填的 slug/name 语义没有超出 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?

描述以具体动词+资源开头（"创建/更新本人公司"），并说明了关键范围限制（"一人一家，立即公开且触发异步处理"），这将其与 update_my_company、create_organization 等同级工具区分开来。不过 "创建/更新" 的双重表述让主要操作（插入还是更新）略显模糊。

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?

描述给出了明确的前置条件与顺序（"登录；确认后"），并提供了工作流链路 read_my_profile→确认资料→create_company→complete_onboarding，能有效指导代理何时调用以及调用顺序。缺少的是何时不应调用（已有公司时应改用 update_my_company）的显式说明。

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