fetch_assessment_runs

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

No annotations, but description discloses pagination behavior, default page, retry on timeout, and covers possible errors. It also fully lists return fields. However, it does not explicitly state read-only nature or rate limits.

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 contains redundant formatting (extra bullet lists) and some repeated info (e.g., page/pageSize explained twice). Could be trimmed to fewer sentences while retaining clarity.

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 output schema present and all return fields listed, description covers parameters, errors, pagination, retry logic, and usage context. No critical information missing for an agent to invoke correctly.

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?

Input schema has 0% description coverage, but description fully explains each parameter: id as assessment id, page and pageSize with defaults and usage. This compensates completely for the schema gap.

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 clearly states the tool fetches all assessment runs for a given assessment ID, and distinguishes itself from fetch_recent_assessment_runs by specifying when to use it. Verb 'Get' and resource 'assessment runs' are explicit.

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?

Description provides clear when-to-use guidance: 'use this tool when expected run is got in fetch recent assessment runs tool'. It also gives retry strategy with pageSize. However, it lacks explicit when-not-to-use or alternative tools beyond the one sibling.

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