get_system_status

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

With no annotations provided, the description carries the behavioral disclosure burden. It clearly indicates a read-only retrieval operation (获取) and states that the output is JSON-formatted system status information. It does not mention auth or rate-limit implications, but for a zero-parameter status getter this is a minor gap.

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 compact and front-loaded, with the main purpose stated immediately. There is minor redundancy between the second line and the 'Returns' line, but no significant filler.

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 parameterless status tool with an output schema, the description is largely complete: it names the main return categories and the JSON format. It could be stronger by explicitly routing storage/RSS/version-related queries to sibling tools, but nothing critical is missing for invoking the tool.

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 tool has zero parameters and schema coverage is effectively complete, so there are no parameter semantics for the description to add. The baseline of 4 applies.

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 verb and resource: 获取系统运行状态和健康检查信息, and lists concrete returned categories such as system version, data statistics, and cache status. It is identifiable as the general system-status tool, though it does not explicitly differentiate itself from sibling status tools like get_storage_status or check_version.

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 is given on when to choose this tool over its siblings, many of which also report status (get_storage_status, get_rss_feeds_status, get_current_config, check_version). There are no exclusions, prerequisites, or alternative conditions, so the usage context must be inferred from the name and first line.

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