get_announcements

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

No annotations are provided, so the description must disclose behavioral traits. It only says 'List', implying a read operation, but doesn't specify pagination behavior, data included, ordering, or any access requirements. The description adds no behavioral context beyond what the one-word verb implies.

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, front-loaded sentence with no waste. It effectively communicates the essence without unnecessary detail, scoring high on conciseness.

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 tool with no output schema and no annotations, the description is too sparse to be fully complete. It lacks information about the response structure, default sorting, or any limitations. While the schema covers parameters, the description doesn't provide enough context for the AI to understand what will be returned or how the list behaves.

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 fully describes all three parameters (flat_id, page, items) with clear descriptions, giving 100% coverage. The description repeats the flat scope but adds no additional semantic meaning about parameters or their use. Baseline 3 applies.

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 uses a specific verb ('List') and resource ('community announcements') with scope ('for a flat'), making the tool's purpose unmistakable. It distinguishes itself from similar list tools like list_community_feeds by emphasizing announcements targeted to a flat.

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 description provides no guidance on when to use this tool over alternatives. It doesn't mention any exclusions, prerequisites, or relationships to sibling tools like list_community_feeds or get_banners. The AI agent is left without context for selection.

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