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

Annotations already declare read-only, idempotent, and non-destructive behavior, but the description adds valuable behavioral context beyond annotations: notes are automatically decrypted, sorted in reverse chronological order, and the output is intended for internal use only, with only human-readable fields presented. This fully discloses the key behavioral traits of the tool.

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 core content is only three sentences, but the same text is repeated verbatim under the '# fetch_notes' heading and the '## When to use' section, which is redundant. The 'When to use' heading implies new guidance but actually duplicates the description, adding unnecessary waste.

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 zero-parameter, low-complexity tool, the description is complete: it states the output scope (all notes for the account), the ordering (reverse chronological), automatic decryption, and how the results should be used. Rich annotations cover safety and idempotency, leaving no meaningful gaps.

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 input schema is fully covered (100%). The description adds no parameter details because none exist, so the baseline of 4 is appropriate; there is no semantic gap to fill.

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 'Get' with the resource 'all notes' and clarifies the account scope, which clearly distinguishes it from siblings like get_note (which likely fetches a single note). It also mentions unique behaviors such as automatic decryption and reverse chronological ordering, making the purpose unmistakable.

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 provides clear context: this fetches all notes for the account, and the results should be used internally for tool chaining, presenting only human-readable information. It does not explicitly mention alternatives like get_note for retrieving a single note or state when not to use this tool, but the 'all notes' wording implies the distinction from single-note retrieval.

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