get_all_build_artifacts

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

No annotations provided, so description carries full burden. It discloses that it lists artifacts and can fetch last build, but does not explicitly state it is read-only, require permissions, or describe side effects. Adequate but not detailed.

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?

Description is reasonably concise, front-loading purpose. Includes returns clause. Slightly verbose due to docstring format but overall efficient for the information provided.

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 2 parameters and no annotations, description covers purpose, parameters, and return format (list of artifact metadata). Missing error handling details but sufficient for typical use with output schema existing.

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 description coverage is 0%, so description must explain parameters. It clearly defines fullname as job name and number with default behavior (last build if None). Adds meaning beyond schema types.

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?

Description states 'List the artifacts of a specific build in Jenkins' with specific verb and resource. Clearly distinguishes from siblings like get_build_artifact and get_build_artifact_url, which focus on single artifacts or URLs.

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?

Implies usage by describing function but lacks explicit guidance on when to use this tool versus alternatives (e.g., get_build_artifact). Only mentions when number is None to get last build.

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