motion_custom_fields

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations exist, so description should disclose side effects (e.g., deletion is irreversible, creations affect task/project structure). Description only lists parameter requirements, omitting behavioral traits like permissions, rate limits, or idempotency.

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?

Concise single paragraph with front-loaded purpose. Dense information is well-organized by operation, though could benefit from bullet points for readability.

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?

Given no output schema and 12 parameters, description thoroughly covers parameter requirements but lacks information on return values, error conditions, or workflow context. Complete enough for usage but lacks behavioral depth.

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 all parameters (100% coverage). Description adds value by grouping required params per operation, clarifying conditional requirements (e.g., 'options[] required for select/multiSelect') beyond schema descriptions.

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 states 'Manage custom fields for tasks and projects' which clearly identifies the tool's domain. However, it does not explicitly differentiate from sibling tools like motion_projects or motion_tasks, which could be confused for broader management.

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?

Explicitly lists required parameters per operation (list, create, delete, etc.), providing clear when-to-use guidance. This is highly specific and actionable, covering all operations.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.