enterprise_get_enterprise_main_person_info

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

No annotations are provided, so the description carries full burden. It only describes input parameters but does not disclose behavior such as whether modifications occur, authentication needs, rate limits, or error responses. The tool appears to be a query, but this is not explicitly stated.

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 concise, listing parameters with brief Chinese explanations. It is front-loaded with the purpose sentence. While efficient, the formatting could be improved for readability, but each line serves a purpose.

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?

Given the tool has 4 parameters, no output schema, and no annotations, the description should explain what the tool returns. It only covers input parameters, leaving output format, error handling, and behavior for missing results unspecified. This incompleteness limits an agent's ability to use 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 description coverage is 0%, but the description adds significant meaning: it explains matchKeyword as '企业名称/注册号/统一社会信用代码/企业id', enumerates keywordType values, and clarifies pageIndex and pageSize. This goes well beyond the bare 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?

The description explicitly states '查询企业主要人员信息' (query enterprise main person info), providing a clear verb and resource. Among sibling tools like enterprise_get_enterprise_base_info and enterprise_get_enterprise_branch_info, this one specifically targets main person info, distinguishing its purpose.

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 lists parameters but provides no guidance on when to use this tool versus alternatives. There is no mention of use cases, prerequisites, or when not to use it. The sibling tools suggest different enterprise information endpoints, but no explicit criteria for selection.

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