list_sites

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

The description discloses the return content (domain, root directory, running status). Since no annotations are provided, the description carries the burden, and it adequately describes what the tool does. However, it does not mention any potential side effects or limitations, though for a read-only list tool this is sufficient.

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: two sentences, no filler. The first sentence states purpose and output, the second gives usage guidance. Every word earns its place.

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 no output schema, the description adequately specifies the return fields (domain, root directory, running status). The search parameter behavior is fully explained. For a simple list tool with one optional parameter, the description is complete and actionable.

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?

The input schema describes the 'search' parameter as '按网站名称或域名模糊搜索' (fuzzy search by name or domain). The description adds '不填则返回所有网站' (if left blank, returns all sites), which clarifies default behavior beyond the schema. With 100% schema description coverage, the baseline is 3, and the added detail justifies a 4.

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: '列出宝塔面板中所有托管的网站，包括域名、根目录、运行状态。' (List all hosted websites in BT panel, including domain, root directory, running status.) It distinguishes from siblings like list_domains by specifying the included fields.

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 provides explicit usage guidance: '查询日志前先用此工具确认网站名称和路径。' (Before querying logs, use this tool to confirm website name and path.) This tells the agent when to use this tool, adding contextual value.

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