get_task_history

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

No annotations are provided, so the description carries full burden. It describes what data is returned (status history, assignment history, milestones, activity summary) and includes examples with time ranges, but does not disclose behavioral traits like rate limits, authentication needs, or error handling. It adds some context but lacks comprehensive behavioral details.

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 well-structured with a clear purpose statement, bulleted list of return components, and practical examples. It is front-loaded and efficient, though the examples could be slightly more concise (e.g., redundant '1 hours=24' typo).

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 tool's moderate complexity, 100% schema coverage, and presence of an output schema, the description is fairly complete. It covers purpose, return data, and parameter usage, but could improve by adding more behavioral context (e.g., permissions, limits) since no annotations are provided.

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 100%, providing good documentation for task_id and hours. The description adds value by explaining the default 30-day history and giving examples with different hour values, clarifying practical usage beyond the schema's technical details.

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 clearly states the verb 'Get' and resource 'comprehensive history for a specific task', specifying it returns aggregated task history with detailed components. It distinguishes from siblings like get_task (likely basic info) or get_recent_activity (broader scope) by focusing on historical data for one task.

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 description implies usage for retrieving historical data on a specific task, but does not explicitly state when to use this vs. alternatives like get_task (for current state) or get_recent_activity (for general activity). The examples show parameter usage but lack contextual guidance on tool selection.

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