karea_view_task

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

Declares read-only nature, lists returned fields, and explains the behavior of includeContext parameter (inlines context vs. hints at existence). No contradictions with annotations (none provided).

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?

Two concise sentences, no wasted words. Front-loaded with main purpose, followed by key option. Every sentence is informative.

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?

Lists main fields returned, adequate for a read tool. No output schema, but description compensates. Slight gap: could mention if projectId is required for visual IDs, but schema already clarifies.

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 has 100% coverage, but description adds context: explains that task can be visual ID, name, or UUID, and describes the effect of includeContext. Adds value beyond schema.

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?

Clearly states it returns one task with full details, lists specific fields, and explains how to locate the task by visual ID, name, or UUID. Distinguishes from karea_get_context by offering an option to inline AI context.

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?

Provides when to use (need full details of a single task) and when to use includeContext to avoid a separate call. Implicitly differentiates from list tools by specifying 'one task'. Could be improved with explicit when-not-to-use.

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