list_newsList an association's news posts newest first, and search them by keyword to find relevant updates.
List the association's news posts, newest first.
| Name | Required | Description | Default |
|---|---|---|---|
| page | No | ||
| search | No |
| Name | Required | Description | Default |
|---|---|---|---|
| result | Yes |
Changes observed during successful MCP inspections.
v0.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is covered. The description contributes the useful 'newest first' sort guarantee, but says nothing about page size, pagination limits, or what the search parameter matches.
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?
A single front-loaded sentence with the resource and the sort order; nothing is padded or redundant.
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?
An output schema exists, so return values need no explanation, and the read-only annotations cover safety. Still missing for a paginated, searchable list tool is any indication of result volume, page size, or search semantics, which leaves the agent guessing about how to iterate results.
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 description never mentions the two parameters, so neither 'page' nor 'search' gets meaning beyond its bare name and default. The names are somewhat self-explanatory, but the description adds no semantics such as page size, search scope, or behavior when search is null.
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?
States a specific verb (List) and resource (the association's news posts) and adds ordering (newest first), so the agent knows exactly what is returned. It does not explicitly differentiate from the sibling get_news, leaving the list-vs-single-item distinction to inference from the verb.
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?
There is no when-to-use guidance at all: nothing about when to prefer this over get_news, when to page through results, or what the search parameter is for. The only signal is the imperative 'List', which the agent must interpret unaided.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.