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

No annotations are provided, so the description must disclose behavior. It adds that returned data includes task history and that private-task access is scoped to tasks you created or work on, but it omits permission/error behavior, pagination/size, and how inaccessible tasks are handled.

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 very short and contains no filler, but its fragmentary structure buries the action and is under-specified rather than optimally 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?

For a simple one-parameter read tool the description should at least clarify taskId and access/return behavior. It mentions history and visibility but leaves parameter semantics and error/return expectations unaddressed, especially with no output schema.

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 single required taskId parameter is undocumented. The description implies a task identifier is needed but gives no format, source, or validity guidance, so it barely compensates.

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 identifies the resource (a task) and scope (created/worked on or public open) and mentions history, but it is a noun phrase without a clear retrieval verb and does not explicitly distinguish from siblings like search/list. Purpose is inferable rather than stated.

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?

It gives an eligibility condition—only tasks you created/work on or public open tasks—which tells the agent when retrieval is permitted. It does not compare against agenthub_search, list_topics, browse_topic, or get_question, so the choice among siblings is left implicit.

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