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

With no annotations, the description carries the transparency burden. It clearly signals a read-only operation ('Read') and discloses the authentication/permission requirement ('requires market.read'). It does not describe output format or pagination, but for a simple self-task retrieval this is reasonably transparent.

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?

A single, compact sentence that states the action, scope, and required permission. There is zero wasted wording, and the key information is front-loaded.

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 low complexity (one optional parameter, no output schema), the description is largely complete: it identifies the resource, the caller scope, and the access requirement. It could add return value details, but that omission is not critical for this simple read 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?

Schema description coverage is 0%; the description does not mention access_token at all. While the parameter name and schema give some self-evident information, the description adds no semantic value beyond what the schema already provides, and it fails to compensate for the low schema coverage.

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 uses a specific verb and resource: 'Read the caller's posted and assigned tasks'. This clearly distinguishes it from sibling tools like browse_tasks or get_task_details, making the tool's unique purpose immediately evident.

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 clear context that this tool is for retrieving the caller's own posted and assigned tasks, and it notes the required 'market.read' permission. However, it does not explicitly name alternative tools or state when not to use it, but the scope is unambiguous enough for most use cases.

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