enterprise_get_enterprise_branch_info

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

No annotations provided, and the description does not disclose behavioral traits such as read-only nature, rate limits, or effects. For a query tool, basic safety is implied but 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 brief (one line plus parameter list) and to the point. It front-loads the purpose and lists parameters clearly, but could be more structured with formatting for clarity.

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?

The tool has no output schema and limited description. While parameter info is provided, the return format, pagination behavior, and error handling are not explained. For a moderately complex tool, this is adequate but not complete.

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 meaning by explaining matchKeyword (企业名称/注册号/统一社会信用代码/企业id) and keywordType (name, nameId, etc.). However, pageIndex and pageSize are only listed without additional context like defaults or range.

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 branch information), which clearly indicates the verb and resource. It distinguishes from sibling tools like enterprise_get_enterprise_base_info and enterprise_get_enterprise_business_info.

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?

No guidance on when to use this tool versus alternatives such as enterprise_get_enterprise_base_info or enterprise_get_enterprise_profile. The description only explains parameters, not usage context or exclusions.

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