fetch_recent_assessment_runs

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

No annotations are provided, and the description only states the function returns a list of runs. It does not disclose whether the call is read-only, destructive, or has authentication or rate limit implications. The return type is mentioned but behavioral traits are missing.

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 structured with clear Args/Returns sections and front-loaded with the primary purpose. However, the extensive return field list could be shortened if an output schema is available.

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 the simple input and provided output details, the description is mostly complete. However, it lacks usage guidance and behavioral context, which are important for an agent to correctly invoke the tool.

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 description restates the sole parameter 'id' as 'assessment id', adding no semantic value beyond the schema. With 0% schema description coverage, the description should elaborate on expected format or examples, which it does not.

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 the tool fetches recent assessment runs for a given assessment ID. However, it does not define what 'recent' means or differentiate from sibling tools like fetch_assessment_runs, which may return all runs.

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 versus alternatives (e.g., fetch_assessment_run_details for a specific run, fetch_assessment_runs for all runs). The description lacks context for appropriate selection.

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