list_worksList works by author, category, or title/summary query.
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No | ||
| query | No | Optional text filter for titles and summaries. | |
| author | No | Optional author slug or name, e.g. cicero, seneca. | |
| category | No | Optional category, e.g. philosophy, speeches, letters, poetry, history. |
| Name | Required | Description | Default |
|---|---|---|---|
| works | No |
Changes observed during successful MCP inspections.
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=true and destructiveHint=false, so description adds little behavioral context beyond 'List works'. Does not mention pagination (limit parameter) or behavior when no filters applied. No contradiction.
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 efficient sentence with no wasted words. Front-loaded with verb+resource.
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?
With output schema present, description need not explain return values. Adequately covers core functionality for a simple listing tool; could optionally mention limit default but schema handles it.
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 covers 3 of 4 parameters (75%) with descriptions. Description groups parameters ('by author, category, or title/summary query') but does not add new meaning beyond schema. Baseline 3 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?
Description clearly states the tool lists works and can filter by author, category, or title/summary query. It distinguishes from siblings like get_work (single work) and search_corpus (full-text search).
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?
Description implies usage for filtering works but does not explicitly state when not to use it or compare to alternatives like get_work or search_corpus. Context is implied but not explicit.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.