medeval_get_generation_task

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, covering the safety profile. The description adds that the tool reads progress, output metadata, and adopted artifacts, which is useful context beyond the annotations. However, it does not disclose any additional behavioral details like pagination, rate limits, or what 'adopted artifacts' entails, so it adds only modest value per the lower bar set by the annotations.

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 redundant words or fluff. It is concise and structured, but it is arguably too terse—leaving out details that could be added without much verbosity. A 5 would require a bit more substance while maintaining conciseness.

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 tool's simplicity (one parameter, output schema present, annotations covering safety), the description is partially complete. It does not explain how to obtain a valid task_id or what 'generation task' specifically refers to, and it lacks usage context relative to siblings. The output schema covers return values, so that is not needed. Overall, it falls short of being fully self-contained for an agent.

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 only one parameter, task_id, with zero description coverage (0% schema_description_coverage). The description does not mention task_id at all, nor does it clarify that task_id identifies the generation task. Since schema coverage is low and the description fails to compensate, the agent must infer the parameter's meaning from the tool name and context. This is a notable 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?

The description clearly states a read operation on a generation task, specifying three aspects: progress, output metadata, and adopted artifacts. The verb 'Read' and resource 'generation task' are explicit. However, it does not distinguish itself from sibling tools like medeval_get_task_progress or medeval_get_run, which could overlap in purpose. A 5 would require naming the distinct resource or excluding alternatives.

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 provides no guidance on when to use this tool versus alternative tools. There is no mention of prerequisites, such as how to obtain a task_id, nor any exclusions. The agent must infer usage from the name and sibling context, which is not explicitly stated.

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