message_get_system

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

With no annotations and a terse description, behavioral traits such as side effects, permissions, or rate limits are absent. The description only states it retrieves a list, adding no depth to what the agent needs to know for safe invocation.

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 very concise (one sentence), which is efficient, but it is too brief to be fully useful. It sacrifices necessary detail for brevity.

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 lack of output schema, parameter documentation, and behavioral hints, the description is incomplete. The agent cannot confidently use this tool without additional information.

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% and the description does not explain the 'pagesize' parameter at all. The agent is left to infer its meaning solely from the schema, which lacks any description.

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 '获取' (get) and the resource '系统消息列表' (system message list), making the tool's purpose straightforward. It distinguishes itself from sibling tools like message_get_post by specifying 'system' messages.

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 provided on when to use this tool compared to alternatives. There is no mention of context, preconditions, or exclusions, leaving the agent without decision-making support.

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