Announcements

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

Adds concrete behavioral detail beyond the annotations: caps of 5 posts per forum and 10 forums, plus fault tolerance ('a course or forum the school server will not open is left out and the rest still shows'). This resilience disclosure is genuinely useful and not derivable from readOnlyHint/openWorldHint.

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?

Front-loaded with the intent question and scoped limits before parameter guidance. The closing 'Ask: ...' sentence partly repeats the opening question, a small redundancy, but the rest earns its space.

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 single-optional-parameter read tool with annotations and no output schema, the description covers purpose, default scope, and partial-failure behavior adequately. Only minor gaps remain, such as ordering of results.

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 coverage is low, but the description compensates by explaining course_ids is optional and that omitting it covers all current courses, and the schema itself notes using get_my_courses to find IDs. It doesn't clarify accepted string-vs-number ID forms, a minor gap.

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 and resource ('Lists the latest news forum posts') with the exact fields returned (subject, course name, text), clearly distinct from all siblings like get_my_courses and get_assignments.

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?

Explains the triggering intent ('any new announcements?') and clarifies course_ids is optional, defaulting to all current courses when omitted. It does not name any alternative or exclusion criteria, but no sibling tool overlaps with this purpose.

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