fetch_assessment_run_details

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

The description details return fields and warns about large output ('store it in a file'), but the pagination advice is inconsistent with the schema. With no annotations, it partially discloses behavior but lacks clarity on the missing page parameter.

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 front-loads the purpose but then provides an extensive list of return fields. While informative, it is verbose for a tool with an output schema. The structure with Args and Returns is clear.

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?

The description covers return fields and large output handling, but lacks context on how to obtain the assessment run ID, potential errors beyond the error field, and pagination details. It is adequate but not fully complete.

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 parameter (id) with 0% coverage. The description adds meaning by labeling it as 'Assessment run id', which clarifies its purpose. However, the reference to a non-existent 'page' parameter detracts from clarity.

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 assessment run details for a given ID, using a specific verb and resource. However, it mentions pagination ('use page to get details pagewise') but the input schema lacks a page parameter, causing slight ambiguity.

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?

No guidance is provided on when to use this tool compared to siblings like fetch_assessment_runs or fetch_run_controls. The description does not specify prerequisites or alternative scenarios.

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