dropbox_sign_list_templatesList reusable templates the account can access. Paginated. API: GET /template/list.
| Name | Required | Description | Default |
|---|---|---|---|
| page | No | Page number to return. Default 1. | |
| query | No | Search string to filter templates (e.g. title). | |
| page_size | No | Results per page (max 100). Default 20. | |
| account_id | No | Account id whose templates to list (defaults to the caller). |
Changes observed during successful MCP inspections.
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
ReadOnlyHint annotation, consistent with description. Adds pagination details and API endpoint, though could disclose more about response behavior.
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?
Extremely concise single sentence with API reference; every word is informative with no repetition.
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; description lacks details on return format, pagination structure, or error handling. Could be more informative given tool complexity.
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 coverage is 100% with clear parameter descriptions. Description adds no additional parameter semantics, so 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?
Description clearly states verb 'list' and resource 'reusable templates', distinguishing from sibling tools that get a single template or list signature requests.
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?
No explicit when-to-use or alternatives provided; only 'Paginated' implicitly suggests listing use case.
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.