lokalise_list_queued_processes

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

With no annotations, the description should convey read-only nature and side effects. It mentions status tracking and return fields but does not explicitly state it is read-only or require no special permissions. Adequate but not fully transparent.

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 concise with two sentences and bullet-like formatting. Front-loaded with key action. Every sentence adds value, though structuring as plain text could be improved.

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 3 well-documented parameters and no output schema, the description covers purpose, usage, and return fields adequately. Lacks detail on pagination but schema covers it. Fairly complete 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 coverage is 100%, baseline 3. The description restates required and optional parameters but adds only minor context (branch notation for projectId). Does not add significant meaning beyond schema.

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 explicitly states 'Lists all background/async processes' with a specific verb and resource, and distinguishes from sibling tools that list other entities like keys or projects. It also provides context on use cases.

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 clear use cases (monitor uploads, downloads, bulk operations, troubleshoot) but does not explicitly state when not to use it or name alternatives. However, the context is sufficient.

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