list_pending_translations

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 does add an access restriction ('PRO plan or higher'), which is useful, but it leaves out response format, workspace/user scope, pagination behavior, and any read-only guarantee beyond the verb 'List'. These are significant gaps for a tool with no annotation support.

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 two short sentences with the core purpose front-loaded. The plan restriction is concise and the text contains no filler or repetition, making it highly efficient.

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 zero-parameter list tool, the description is minimal but adequate. However, with no output schema and no annotations, it does not explain return format or clarify what 'pending' means in the translation workflow (e.g., awaiting approval), and it omits workspace scope. It has clear gaps but covers the essential purpose and a key access restriction.

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 tool has zero parameters, so the input schema already provides complete parameter coverage. With no parameters to document, the description has nothing to add, and the baseline of 4 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?

The description 'List pending translations' uses a specific verb ('List') and resource ('pending translations'), clearly distinguishing it from sibling tools like get_translation, upload_translation, approve_translation, and delete_translation. The 'PRO plan or higher' qualifier is supplementary and does not muddy the core purpose.

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 such as approve_translation or get_translation. The only added context is 'PRO plan or higher', which is a plan prerequisite rather than usage direction, so the description gives no exclusions or alternative tool references.

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