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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the safety profile is covered. The description does add one genuinely useful behavioral fact not in the annotations: results are scoped to data visible to the linked Market Brew account. It says nothing about pagination despite query supporting offset/pageSize, so it stops short of rich behavioral context.

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 short sentences, no bloat, and the usage trigger is front-loaded. The only weakness is that the first sentence largely duplicates the title, so not every word earns its place.

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?

There is no output schema, so the description needn't explain return values, and the visibility constraint is a helpful addition. However, for a tool with a nested query object supporting filters and pagination, it never explains the parent/child relationship versus list_tasks, nor how paging works. Just barely complete enough to call correctly.

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 only 50%; the required taskId parameter has no description in the schema and is never explained in the description either. The description adds zero parameter meaning — no mention of the parent task identifier, the query filter object, or pagination fields. With half the parameters undocumented and no compensating prose, this falls below the baseline.

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 says it lists child tasks, which matches the name and title, but it is close to a restatement rather than a distinct specification. It offers no differentiation from the many siblings that also list or fetch tasks (list_tasks, list_task_history, get_task), so an agent cannot tell from the text alone why it should pick this one. Purpose is implied but vague about scope (e.g., what counts as a 'child').

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?

"Use this when the user asks to list child tasks" gives a trigger condition, but that trigger is essentially the tool's purpose restated. It never names an alternative (list_tasks, list_task_history, get_task) or states when-not to use it, leaving the routing decision to inference. Adequate as implied usage only.

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