List brand mockup jobs

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

Since no annotations are provided, the description carries the behavioral burden. It discloses read-only nature, required permission scope, ordering, and included fields (status, progress, errors, result URLs). This goes beyond a minimal description, though it omits details like pagination.

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?

Three short sentences immediately convey purpose, ordering, content, and permissions. No filler or redundant information.

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?

For a simple list tool with one parameter and no output schema, the description covers the core behavior, expected fields, and access requirements. It may not mention pagination limits, but overall it's sufficiently complete for an agent to decide when to invoke.

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 only parameter projectId is fully documented in the schema with description 'Owned brand project id from list_brand_projects.' Since schema coverage is 100%, the description adds little beyond the tool's own mention of 'one brand project'.

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 uses specific verb 'List' with resource 'mockup jobs' and scope 'one brand project's', also mentions ordering 'newest first' and content. This distinguishes it from sibling get_mockup_job which fetches a single job.

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?

States it lists one brand project's jobs, implying you need a projectId from list_brand_projects (defined in schema). Also says 'Read-only' and 'Requires kits:read', giving context on when it's safe to use. However, it does not explicitly name alternatives or exclusions.

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