task_render

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

With only readOnlyHint=false declared, the description carries most of the burden and does add real context: the default action writes a rendered Markdown view, while check=true is non-writing and fails on drift. It still omits where the file is written and whether it overwrites an existing view, but the mutation semantics are disclosed clearly and consistently with the annotation.

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?

One compact sentence, front-loaded with the action and artifact, then the mode modifier. Nothing is redundant or padded; every clause conveys distinct information.

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?

No output schema and minimal annotations, so the description is the only source of behavioral detail. It covers the two modes well but leaves gaps an agent would care about: output location/filename, whether it depends on a prior task_validate, and what 'drift' is measured against.

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?

Schema coverage is 0% and the lone parameter is undocumented structurally, so the description must compensate. It does: 'check=true fails on drift instead of writing' gives both the meaning and consequence of the flag, including the default write behavior implied by 'instead of writing'.

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?

States a specific verb+resource ('Render the Markdown view from tasks.json') and names the source artifact, which no sibling mentions. It is distinguishable from task_list/task_validate in resource terms, though it never explicitly contrasts with task_validate, whose drift-checking role sounds adjacent.

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 'check=true' clause implies a mode choice (verify vs write), which is useful conditional guidance. But there is no explicit statement of when to prefer this tool over task_validate or quality_check, and no stated prerequisites.

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