list_installed_docsets

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

With no annotations provided, the description carries full burden and adds valuable behavioral context: it discloses that results are automatically truncated if exceeding 25,000 tokens and specifies the return condition for no installed docsets. This goes beyond basic functionality, though it could mention performance or error handling.

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 front-loaded with the core purpose in the first sentence, followed by two concise sentences adding critical behavioral details. Every sentence earns its place with no waste, making it efficient and well-structured.

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 the tool's simplicity (0 parameters, output schema exists), the description is largely complete. It covers purpose, edge cases (empty list), and a key limitation (token truncation). With an output schema, it need not explain return values, but could slightly enhance by mentioning format or ordering.

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 0 parameters with 100% schema description coverage, so the schema already fully documents inputs. The description appropriately does not add parameter details, maintaining focus on behavior. Baseline is 4 for zero parameters, as it avoids unnecessary repetition.

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 specific action ('List all installed documentation sets in Dash') and resource ('documentation sets'), distinguishing it from siblings like search_documentation or load_documentation_page. It provides precise scope by specifying 'installed' and the context of Dash.

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 installed docsets, but does not explicitly state when to use this tool versus alternatives like search_documentation. It mentions an empty list result condition, which gives some context, but lacks explicit guidance on scenarios or prerequisites.

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