List available documents in the self-reliance library, optionally filtered by category to locate specific topics.
List the documents in the library, optionally limited to one category slug.
| Name | Required | Description | Default |
|---|---|---|---|
| category | No | Category slug, or empty for every document. |
Changes observed during successful MCP inspections.
v0.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations provided, the description carries the disclosure burden. It accurately conveys that this is a read-only listing operation with optional category filtering, but it does not mention behaviors such as response format, pagination, ordering, or behavior for invalid or empty categories. This is acceptable for a simple list tool but not fully transparent.
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 a single, front-loaded sentence with no filler. It communicates the core operation and the optional parameter clearly, and every word contributes to understanding.
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 tool with one optional parameter and no output schema, the description provides enough to make a basic call. It falls slightly short of complete because it does not clarify how this relates to homestead_search or homestead_catalog, nor what the returned document list looks like.
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 description coverage is 100%, so the single 'category' parameter is already well documented. The description adds only the phrase 'optionally limited to one category slug,' which mostly restates the schema rather than providing new semantic meaning. 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 description states a clear verb ('List'), a specific resource ('documents in the library'), and an optional scoping condition ('limited to one category slug'). It is easy to understand what the tool does, though it does not explicitly differentiate it from siblings like homestead_search or homestead_catalog.
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 does not say when to use this tool versus alternatives such as homestead_search or homestead_catalog. There is no when-to-use guidance, exclusion context, or mention of sibling tools, so an agent must infer the appropriate choice from the tool name and minimal wording.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.