slc_endpoints

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

No annotations are provided, so the description carries the full burden. The description discloses the output fields (id/家族/路径/参数) and the optional filter, but it does not explicitly mention that the operation is read-only or non-destructive. Since 'list' naturally implies a read operation, it is adequate but not rich.

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 a single, concise sentence that front-loads the main purpose ('列出全部可用 webapi 接口'), then specifies the fields and filter capability, and ends with the intended use. Every phrase earns its place without 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?

Given the tool's simplicity (one optional parameter, no output schema, no annotations), the description is complete: it states what is returned and the filter option. It lacks some details like return format or pagination, but for a discoverability tool, this is adequate. The sibling context reinforces that this is a meta-tool for finding other APIs.

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 coverage is 100% with the one parameter 'family' already described in detail, including examples. The description only says '可按 family 过滤' (can filter by family), adding no new semantic information beyond the schema. Thus, 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 tool's purpose: '列出全部可用 webapi 接口' (list all available web API endpoints), and specifies the resource (webapi interfaces) and the action (list). It also distinguishes itself from siblings by indicating it provides discovery of endpoints, while siblings are specific data tools like souyun_rhyme and slc_datasets.

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 includes '用于发现能力' (for discovering capabilities), which implies when to use this tool: when the agent needs to know what APIs are available. It also mentions filtering by family, but it does not explicitly state alternatives or scenarios where this tool should not be used. This is sufficient for a discovery tool.

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