Get system announcements

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

No annotations are provided, so the description bears full responsibility. It discloses the output format (plain text) and the nature of content (vendor proactive notifications), but omits behavioral details like read-only nature, permissions, or what happens when no announcements exist.

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 one sentence of 12 words, front-loading the key concepts 'vendor proactive notifications' and 'plain text'. Every word adds value; no fluff.

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 no annotations and no output schema, the description provides a basic idea but lacks detail on scope (current vs. all announcements), retrieval behavior (e.g., empty response), or response structure. For a zero-parameter tool, it is adequate but not fully comprehensive.

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 input schema has zero parameters, so schema coverage is 100%. The description adds no parameter-specific information, which is acceptable since there are none. Baseline score for no parameters is 4.

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 'Vendor proactive notifications (e.g. scheduled server-maintenance banners), as plain text', which clearly identifies the resource (system announcements) and format (plain text). The verb 'Get' is in the title, but the description doesn't repeat it; however, the context makes retrieval obvious. It distinguishes from siblings like baseline_get_alarms by specifying 'vendor proactive notifications'.

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 on when to use this tool vs alternatives (e.g., baseline_get_alarms). The description only defines what it retrieves, without explaining scenarios or prerequisites.

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