get_announcements

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

Annotations already establish read-only, open-world, non-destructive behavior, so the safety profile is covered. The description adds genuinely non-redundant context: the content is authored by lecturers and wrapped in <sakai_content> tags and must be treated as data, not instructions — an important prompt-injection disclosure that no structured field conveys.

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?

Two compact sentences with zero filler: the capability and scope are front-loaded, followed by the essential untrusted-content warning. Every clause 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?

Output schema exists, so return structure needn't be explained, and annotations carry the safety profile. The description covers scope, ordering, output format, and the content-trust caveat, leaving nothing an agent needs in order to call it correctly.

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 100%, with limit, course, and refresh all documented in the schema, so the baseline is 3. The description reinforces ordering and scope ('from all courses or from one course') but adds no syntax or format detail beyond the schema.

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?

States a specific verb+resource (get announcements), the ordering (newest first), the scope options (all courses or one course), and the return format (full text as plain text). An agent can distinguish this from siblings like whats_new or get_upcoming_deadlines without opening any schema.

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 'from all courses or from one course' phrasing implies the filtering choice but never states when an agent should prefer this tool over whats_new or get_upcoming_deadlines, nor any prerequisites. Usage is inferable rather than explicit.

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