list_announcements

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

Beyond the readOnly/idempotent annotations, the description explains visibility rules for admins vs regular users, the 7-per-page cap, offset pagination semantics, and the exact return structure. This gives the agent a full behavioral picture.

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 organized into concise sections (overview, visibility, args, returns) with no filler. Each sentence adds operational value, and the critical pagination detail is front-loaded.

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?

With only one optional parameter and clear annotations, the description fully covers invocation, pagination, visibility, and return shape. There is no missing information an agent would need to call this 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?

The schema only says offset is an integer with default 0; the description adds crucial meaning: offset is an announcement ID, pass the smallest ID from a previous call to get older items, and default 0 starts from newest. This fully compensates for the 0% schema coverage.

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 clearly states the action (list announcements), the resource (Nextcloud Announcement Center), and key behavioral details (visibility, sort order, pagination cap). It is easily distinguished from siblings like list_notifications or create_announcement.

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 gives clear context on what the tool returns and who sees what, but it does not explicitly name alternatives or state when not to use it. The usage is obvious from the resource and behavior, but exclusion guidance is absent.

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