jcourse_list_announcements

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

Annotations already declare this as a safe, idempotent, non-destructive read, so the safety profile is carried. The description adds one genuine behavioral fact — that only currently-valid announcements are returned ('当前有效') — but says nothing about ordering, volume, or whether expired/pinned announcements are included.

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?

One front-loaded sentence naming the verb, the resource, and the returned fields — no filler, nothing an agent must scroll past.

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?

An output schema exists, so the description needn't enumerate return values, and the annotations cover the safety contract. For a parameterless read tool this is close to sufficient; only the 'what counts as active' filter and result ordering are left implicit.

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 takes zero parameters, so there is no parameter semantics to explain; the baseline score applies. The description correctly implies no input is needed by simply listing what is read.

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?

Names a specific verb and resource ('读取...公告') plus the fields involved (time, priority, external link). The announcements domain is clearly distinct from the course/review/teacher siblings, though the description doesn't explicitly state the distinction.

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?

Usage is only implied — an agent can infer it should call this to see site announcements. There is no explicit when-to-use, no prerequisites, and no mention of how it relates to jcourse_get_system_settings or the auth tools, which are the nearest neighbours in the site-metadata family.

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