List dictionary words

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

Annotations already declare readOnlyHint=true, so the safe-read behavior is covered. The description adds meaningful context beyond annotations: it identifies the dictionary as local to the OpenWhispr app and discloses that the return value includes both the words and the shape in which they were stored. This adds helpful behavioral detail without contradicting the annotations.

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 two sentences, with the core action and resource front-loaded. The second sentence adds the return-value shape without redundancy. Every part earns its place and there is no filler.

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?

With no parameters, no output schema, and read-only annotations already provided, the description covers what the tool does and what it returns. An agent has enough context to select and invoke this tool correctly without further elaboration.

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, so there is nothing for the description to elaborate on. The baseline for no parameters is 4, and the description appropriately focuses on the output semantics rather than inventing parameter guidance.

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 states a specific verb ('List') and a specific resource ('the custom dictionary of the local OpenWhispr app'), and clarifies the purpose: it shows words the transcriber is told to spell a particular way. This clearly distinguishes it from sibling tools such as update_dictionary and list_notes.

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 makes the read-only listing purpose clear, and the sibling context includes update_dictionary as the obvious write counterpart. However, it does not explicitly say 'use this when you need to view the dictionary' or mention any alternative or exclusion, so usage guidance remains mostly implied rather than stated.

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