ak_get_run

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

With no annotations, the description carries the burden of disclosing behavior. 'Get' conveys a non-mutating read and 'one' conveys singleton cardinality, but it does not disclose not-found behavior, required permissions, or what the returned run looks like. This is adequate but not rich.

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 a single front-loaded sentence with no filler or redundancy. Every word contributes to the tool's purpose and invocation condition.

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?

For a one-parameter read tool, 'Get one run by id' plus the schema's required runId is sufficient for an agent to invoke it correctly. It does not cover error cases or return details, but the low complexity and clear sibling context make those gaps minor.

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?

The schema has one required string parameter, runId, with 0% description coverage. The phrase 'by id' maps runId to the run's identifier, adding a small amount of meaning, but it does not explain format, origin, or lookup semantics beyond what the parameter name already implies.

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 uses a specific verb ('Get'), a concrete resource ('run'), and a selection criterion ('by id'), so an agent can distinguish this from ak_list_runs (all runs) and ak_get_project (another entity). The one-sentence definition fully identifies the tool's function.

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?

'Get one run by id' clearly establishes the condition for using this tool: the agent has a runId and wants a single run. It does not explicitly contrast with ak_list_runs, but 'one' versus the sibling name 'list' makes the intended context apparent without ambiguity.

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