profilarr_list_announcements

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

Annotations already declare readOnlyHint=true, which the description does not contradict. The description goes beyond the annotation by explaining the filtering behavior (withdrawn/expired/version-incompatible) and sort order (newest first), providing useful context for the agent.

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 that conveys the action, scope, and ordering with no wasted words. Every element adds value.

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 the tool's simplicity (zero params), the read-only annotation, and the presence of an output schema, the description sufficiently covers the essential behavior. The filtering and ordering details make it complete for its scope.

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 tool has zero parameters and the schema coverage is 100% (trivially). The description does not need to explain parameters, and the baseline score of 4 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 the specific verb 'list' with resource 'announcements', and adds clear qualifiers: only visible ones (withdrawn/expired/version-incompatible filtered) and ordering (newest first). This distinguishes it from the sibling tool 'profilarr_get_announcement' which likely fetches a single 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 clearly states what the tool does and implies when to use it: to get a list of visible/current announcements. However, it does not explicitly name alternatives or exclusion scenarios, though the filtering note implicitly indicates that hidden announcements would require a different tool.

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