company_certlist基于明确指定的企业名称，查询该企业拥有的资质证书信息，包括证书编号、证书类型、发证日期、证书失效日期、证书撤销日期、证书注销日期、证书状态、证书详情等。
Pricing: {"unit": "credits", "billing_model": "per_run", "per_run": 0.2}
| Name | Required | Description | Default |
|---|---|---|---|
| page | No | 指定返回第几页结果，从 1 开始，默认 1；与 limit 配合使用。 | |
| limit | No | 指定单次请求最多返回的记录数，默认 20，最大 100。 | |
| company_name | Yes | 企业名称（必填）。用于查询该企业的资质证书。示例：通威股份有限公司 |
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Beyond the openWorldHint annotation, the description discloses a read-only query behavior, the certificate fields that will be returned, and the per-run pricing model. It does not address edge cases such as exact-match behavior or empty results, but for a simple query tool this is reasonably transparent.
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 one dense, front-loaded sentence stating the action, input, and returned fields, followed by a concise pricing line. There is no filler, redundancy, or repetition of schema details.
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?
For a 3-parameter query tool with full schema coverage and an output schema, the description is sufficiently complete for reliable invocation. Minor gaps are the lack of explicit guidance on when to choose this over company_licensing and clarification of company-name matching behavior, but these are not critical for basic use.
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 100%, so the schema already documents company_name, page, and limit. The description only reinforces that company_name must be explicitly specified and does not add substantive new meaning beyond the schema, so the baseline score of 3 is appropriate.
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 operation ('查询' / query) and the resource ('资质证书信息' / qualification certificate information) for a given company, and lists the certificate-related fields returned. It does not explicitly differentiate itself from the sibling tool 'company_licensing' or other company_* tools, so it stops short of the highest sibling-distinction standard.
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 gives clear usage context: use this tool when an explicitly specified company name is available and you need that company's qualification certificates. It does not mention alternative tools or exclusion cases, so it does not earn a 5.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
大量工具功能高度重叠，例如chain_*和park_*系列均为按不同筛选条件查询企业列表或数量，只是参数不同却拆分为独立工具；enterprise_change_*系列同样针对不同指标逐一拆分。虽然描述清楚各自区别，但代理面对198个工具时极易选错，且许多工具本质应合并为带参数的单一接口。
多数工具采用snake_case加领域前缀（如chain_、park_、company_、gov_data_、poi_data_），但存在明显变体如company_certlist、company_randomin_spection（拼写异常）、corporate_exception_report、due_diligence_report、sg_chokepoint等，混用英文抽象名词与动词短语，整体模式可辨认但不统一。
工具总数高达198个，远超合理范围（即使复杂领域也应控制在25个以内）。大量工具是同一逻辑的不同参数变体（如list/num、不同资质条件），完全可以通过参数化减少数量，严重冗余，代理难以有效浏览和选择。
工具覆盖领域广泛，包括企业信息、产业链分析、园区统计、地区宏观、POI明细、供应链风险、关税计算等，基本覆盖了商业数据查询的主要需求。虽缺少更新/删除等操作（但作为查询服务器可接受），且部分细分领域可能有遗漏，但整体功能较为完整。