List Site Notes (in-context front-end notes)

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

Annotations already declare this as read-only, idempotent, and non-destructive, and the description adds valuable context: the source is the connector's target site, the plugin must be active, notes include specific fields, and results are sorted open-first then priority. This goes beyond what annotations provide.

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 well-organized with a clear purpose, usage context, arg list, and return summary. It is slightly redundant with the schema's arg descriptions, but every sentence is purposeful and the structure is easy to scan.

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?

Even without an output schema, the description explains what the return contains (fields like page URL/title, priority, status, author, timestamp, linked element) and the ordering. It also covers multi-site usage, making it complete for the tool's complexity.

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 already provides 100% coverage with descriptions for all three parameters, including enums and defaults. The description restates the args without adding new details beyond what the schema provides, so the baseline of 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 clearly states the tool lists in-context notes/change-tasks captured on the front end via a specific plugin, distinguishing it from sibling tools like wp_list_posts and wp_list_pages. It names the resource and the action ('List') with sufficient specificity.

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?

Guidance is explicit: use it to sync notes into project tracker/wiki or review outstanding notes, and run on both DEV and LIVE connectors to get the full picture. It also mentions the prerequisite that the companion plugin must be active, which helps the agent decide when to invoke.

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