List library categories with slugs, labels, count data, and safety cautions to select a valid slug for searching or adding documents.
List the library's categories -- slug, label, document and chunk counts, and any safety caution attached to the shelf. Call this to pick a valid slug for homestead_search or homestead_add.
| 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?
With no annotations provided, the description carries the behavioral burden and does disclose the read-only nature via 'List', and it reveals that results include safety cautions attached to shelves. It does not discuss error conditions or access requirements, but for a parameterless listing tool this is a reasonable level of transparency.
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?
Two tight sentences accomplish everything: the first states the operation and its outputs; the second gives the immediate usage guidance. There is no filler, and the purpose is front-loaded.
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 paramless listing tool, this description is complete: it names the output fields, flags the safety-caution element, and explains how the result should be used with sibling tools. Nothing an agent needs to select or invoke it correctly is missing.
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 and the schema covers 100% of them by being empty, so there is nothing the description needs to clarify. The baseline for zero-parameter tools is 4, and no additional parameter guidance is warranted here.
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?
States a specific verb ('List'), a precise resource ('the library's categories'), and enumerates the exact output fields (slug, label, counts, safety caution). The closing sentence ties the tool to its siblings by explaining it supplies slugs for homestead_search and homestead_add, making its role unmistakable.
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 explicitly tells the agent when to call it: to pick a valid slug before using homestead_search or homestead_add. It provides clear context for the primary use case, though it does not enumerate when-not-to-use scenarios or list alternative tools for other needs.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.