list-keywords

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

No annotations are provided, so the description carries the burden. It states keywords are 'sorted by usage count' and that limit caps the output, implying read-only behavior. However, it does not disclose permissions, empty results handling, or rate limits.

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 short sentences, front-loaded with the action 'List keywords', and every word is relevant. No wasted 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?

Given no output schema and 2 optional params, the description covers the tool's purpose and a usage hint. It does not describe return format, but for a simple list tool this is adequate. Slight gap: no mention of what exactly is returned (keyword strings vs objects with counts).

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 coverage is 100%, so both parameters are described in the schema. The description reinforces 'limit' as a cap, but adds no new semantic information beyond what the schema already provides. Baseline 3 is appropriate.

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 tool name 'list-keywords' and description 'List keywords sorted by usage count. Use limit to cap.' clearly specify the verb (list), resource (keywords), and additional details like sorting and limit. It is distinct from sibling tools which deal with albums, folders, persons, etc.

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 a usage hint 'Use limit to cap' but does not specify when to use this tool vs alternatives, nor when not to use it. No explicit alternatives or exclusion criteria are given.

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