list_announcements

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

Annotations already declare readOnlyHint=true, openWorldHint=true, idempotentHint=true, and destructiveHint=false, covering the safety profile. The description adds no further behavioral context beyond confirming it reads announcements; it does not mention pagination, rate limits, or result structure. Since annotations cover the main traits, a 3 is appropriate.

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 a single concise sentence that directly states the tool's purpose without redundancy. It is efficient and front-loaded, with no wasted words.

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?

The description is minimal and does not explain how the optional parameters affect behavior (e.g., what 'recent' means, how course_ids filters). Since the schema lacks descriptions and the output schema is present but not described, the description is incomplete for an agent to call the tool correctly with meaningful arguments.

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 tool description provides no explanation of the three parameters (limit, course_ids, since_days). The description fails entirely to compensate for the lack of schema descriptions, leaving agents without any clue about parameter meaning or usage.

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 states a clear verb ('Lee' / reads) and resource ('avisos recientes de los foros de novedades/anuncios de las materias'), making the tool's purpose understandable. It is specific to announcements from course news forums, which distinguishes it from broader tools like list_notifications or list_forums, though it does not explicitly name alternatives.

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 versus related tools (e.g., list_notifications, list_forum_discussions). There is no mention of context, prerequisites, or conditions that would warrant using this tool over others, leaving the agent to infer usage.

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