list_accounts

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

The description indicates a read-only operation ("List") with no destructive actions. However, no annotations exist to supplement, and the description does not disclose potential error conditions, authorization requirements, or rate limits. For a simple parameterless tool, this is adequate but not enhanced.

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, clear sentence that directly states the tool's function with examples. No extraneous content.

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 simple list tool with no parameters and no output schema, the description fully covers the functionality. It explains what accounts are listed and provides illustrative examples.

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 has zero parameters, so the description adds no parameter-specific information. With schema coverage at 100% (trivially), a baseline of 4 is appropriate per the guidelines.

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 available Apple Notes accounts, with examples (iCloud, On My Mac). It distinguishes itself from sibling list tools like list_folders and list_notes by specifying the resource type (accounts).

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 implies usage for retrieving account names but does not explicitly state when to use this tool over alternatives like list_folders or list_notes. No exclusions or prerequisites are provided.

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