rundeck_get_execution_output

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

No annotations are provided. The description fails to disclose whether the operation is read-only, how logs are returned (e.g., format, streaming), or behavior regarding pagination vs offset/maxlines. The lack of behavioral context is a significant gap.

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 extremely concise with two sentences, front-loading the main purpose. Every word adds value, and there is no redundancy.

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 the complexity of a log retrieval tool with 5 parameters and no output schema, the description is too brief. It does not explain return format, pagination behavior, or error conditions (e.g., if execution not found). The description leaves significant gaps for an AI agent.

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%, so all parameters are already described. The description adds that node and stepctx are for filtering, which is already in the schema. No additional meaning is provided beyond what the schema specifies.

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 tool gets log output from an execution, which is a specific verb and resource. It distinguishes itself from siblings like rundeck_get_execution (execution details) and rundeck_get_job_executions (list of executions) by focusing on log output. The mention of filtering adds specificity.

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 node and stepctx params for filtering, providing some context on when to use those parameters. However, it does not explain when to use this tool versus alternatives, nor does it mention prerequisites like execution state or pagination usage.

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