list_artifacts

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is covered elsewhere. Beyond that, the description contributes essentially nothing — it does not explain ordering of results, whether paging is stable, what happens when offset exceeds the collection, or the shape of returned items.

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?

At four words there is no wasted filler, but this is under-specification rather than conciseness — the fragment lacks a subject and verb and omits information an agent needs. A single well-formed sentence would be both shorter in effort and far more informative.

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?

With a required parameter, two bound-constrained optional parameters, zero schema descriptions, and no output schema, the description carries the full burden of clarification and simply does not deliver. An agent could invoke it but could not predict pagination behavior or how to iterate through results.

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 all three parameters (job_id, limit, offset) are undocumented in the schema, and the description does not compensate. The word "page" weakly implies limit/offset semantics with a default page size, but nothing is said about the required job_id or the 1-500 bounds on limit.

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?

"Page job file inventory" does signal that this retrieves a paginated collection of files belonging to a job, but the phrasing is terse and never uses the word "artifact" from the tool name, leaving the agent to infer that "job file inventory" equals artifacts. It also does nothing to distinguish this from siblings like read_artifact or search_artifacts.

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 no indication of when to choose this over read_artifact (single artifact retrieval) or search_artifacts (filtered lookup), both of which are obvious alternatives. There is no statement of prerequisites, no when-not-to-use condition, and no routing guidance at all.

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