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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered and the bar is lower. The description adds that results are scoped to the authenticated account and sorted newest-first, but says nothing about pagination behavior, default result count, or result contents.

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?

A single front-loaded sentence with zero filler and no repetition of the title's information. It is efficient, though it is efficient partly by saying very little.

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 read-only list endpoint with no output schema, the description never tells the agent the response is paginated or how many items come back by default; pagination is only inferable from the schema's 'before' text mentioning nextCursor. Adequate but with a clear gap for a list tool.

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 50%: 'before' is documented thoroughly in the schema (cursor vs ISO-8601 with the millisecond-skip caveat), while 'limit' carries only type/default/bounds. The description adds nothing about either parameter, but the self-explanatory 'limit' schema and the rich 'before' doc keep the baseline at 3.

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?

States a specific verb and resource ('List ... Clipper jobs') plus scope ('the authenticated Prolifik account's') and ordering ('newest'). It is distinguishable from get_clip_job by the plural/collection framing, though the siblings it differs from are never named.

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 gives no when-to-use guidance, no mention of alternatives such as get_clip_job or get_clip_job_status for single-job status, and no exclusions. The only hint is the word 'newest', which implies a bulk listing.

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