rundeck_get_job_metadata

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

No annotations provided, so description carries burden. It implies a read-only operation, which is non-destructive. However, it does not disclose prerequisites, rate limits, or side effects. Acceptable for a simple read.

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?

Single, concise sentence that efficiently communicates purpose. Front-loaded with key info. Could be slightly more structured with usage note.

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?

No output schema. Description partially covers response fields (creation date, author, modification info). Omits other potential metadata. Sufficient but not comprehensive.

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 100% with one parameter (id) described as 'Job UUID'. Description adds no additional meaning. Schema already covers it, but no examples or format clarifications given.

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 it retrieves job metadata (creation date, author, modification info). The verb 'Get' and resource 'job metadata' are specific. However, it does not distinguish from sibling tools like rundeck_get_job (full job details) or rundeck_get_job_executions.

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 implies usage when a job UUID is known. No explicit guidance on when not to use or alternatives. Siblings exist but are not mentioned.

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