Lists available documentation packages from @particle-academy/* and other scanned packages, showing name, version, source, and file count for version-matched docs.
List every @particle-academy/* (and other scanned) package that has docs available, with name, version, source (node_modules vs workspace), and file count.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Changes observed during successful MCP inspections.
v0.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations provided. Description lists output fields but lacks behavioral details (e.g., pagination, sorting, auth requirements, side effects). Adequate for a simple list tool but not comprehensive.
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?
Single sentence, no redundancy, efficiently conveys purpose and output.
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?
No output schema, but description specifies output fields. Covers core use case; lacks details on ordering or filtering, but acceptable for a list tool.
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?
No parameters; schema coverage is 100%. Baseline for 0 parameters is 4, and description correctly omits param info.
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 'List every @particle-academy/* (and other scanned) package that has docs available' with specific output fields (name, version, source, file count). It distinguishes from siblings like docs_list (likely lists all docs) by specifying packages.
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?
Purpose is clear; an agent can infer when to use (when needing a package list). Implicit distinction from siblings, but no explicit when-not or alternatives. Context from sibling names helps.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.