list_actions

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

The description discloses that the global list keeps only a short window of recent actions, which is a key behavioral trait. However, with no annotations provided, it lacks details on authentication, rate limits, or read-only nature. It partially compensates but is 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 two sentences, front-loaded with the main purpose, and contains no filler. Every sentence earns its place, efficiently conveying key 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?

Given no output schema, the description covers the tool's purpose and usage context well. It could be more complete by hinting at the return format (e.g., list of action objects), but for a simple listing tool with good parameter hints, it is mostly sufficient.

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?

All parameters have schema descriptions (100% coverage). The description adds value by explaining why to use projectName/serviceName filters ('não perder ações'), providing context beyond the schema's basic field descriptions.

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 states the verb 'Lista' and resource 'ações/jobs' with examples (deploys, builds, restarts). It distinguishes the tool from siblings like 'get_action' by implying a list operation, and adds scope context (global vs filtered).

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 advises using filters to avoid losing actions of a specific service due to the global list's short window. This provides clear when-to-use guidance, though it does not explicitly mention when not to use or alternative tools.

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