motion_projects

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

No annotations are present, so the description carries the full burden of behavioral disclosure. It only restates the operation names and does not mention side effects of create, authentication/permission needs, pagination behavior for list, error cases, or response shapes.

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?

The description is a single sentence that front-loads the resource and then lists the supported operations. There is no redundant detail or filler, making it appropriately concise and easy to parse.

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 multi-operation tool with 7 parameters, operation-dependent requirements, no output schema, and no annotations. The description does not explain which parameters apply to which operation in practice, what a successful create returns, how list results are delivered, or any operational limitations.

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 schema already provides descriptions for all 7 parameters, so the baseline is 3. The description adds no additional parameter-level meaning, but it does not need to because the schema coverage is complete and self-explanatory.

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 clearly identifies the target resource, 'Motion projects', and enumerates the exact supported operations: create, list, and get. This makes the tool's scope reasonably obvious and distinguishes it from the sibling tools, which target other Motion resources. However, the verb 'Manage' is broad and could imply update/delete operations that are not actually supported.

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 no guidance on when to use this tool versus alternatives, nor when each operation should be selected. An agent is left to infer usage from the operation enum and parameter descriptions in the schema.

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