List all PDF templates in your workspace, optionally scoping to a specific workspace ID to filter results.
List all PDF templates available in the workspace. Optionally scope the listing to a specific workspace with workspace_id.
| Name | Required | Description | Default |
|---|---|---|---|
| workspace_id | No | Optional workspace (app) ID to scope the template listing. When omitted, uses the default workspace. |
Changes observed during successful MCP inspections.
v1.0.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description must carry behavioral disclosure itself. It does convey that this is a read-only listing operation with optional workspace scoping. However, it does not mention return format, pagination, or error behavior, so it falls short of a higher score.
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 short sentences with no filler, with the core purpose front-loaded and the optional parameter mentioned immediately after. Every sentence earns its place.
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?
This is a simple list tool with a single optional, fully documented parameter, so the description is mostly sufficient. The only notable omission is the return shape or contents of the listing, since no output schema is provided to cover that.
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%, and the schema already explains that workspace_id is optional and defaults to the current workspace. The description only restates this parameter behavior rather than adding new semantic detail.
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 opens with a specific verb and resource: 'List all PDF templates available in the workspace.' This clearly separates it from sibling tools like get_template (single template retrieval) and list_documents/list_snippets (other resource types).
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 provides clear contextual guidance by explaining the optional workspace scoping and the default behavior when workspace_id is omitted. It does not explicitly name alternative tools or exclusion conditions, so it stops short of a 5.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.