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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered. The description adds the semantic content of the log entries, which is useful, but says nothing about ordering, retention window, or how the limit truncates results. That is adequate-but-thin against annotations that already carry the main behavioral burden.

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?

Three short clauses, front-loaded with the purpose and then the log contents and the call-site guidance. "Clone of get_task_history" is a slightly awkward aside but it is compact and serves routing, so nearly 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 parenthetical list of change types effectively stands in for a description of what comes back, and the pre-update usage note covers the agent's decision point. Only the absence of any note on result volume or ordering keeps this from being fully complete for a 2-parameter 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 50%: limit is documented in the schema (1-50, default 20) while issueId is not, though its meaning is self-evident from the name. The description contributes no additional parameter meaning, so it neither compensates for the gap nor overlaps the existing documentation.

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?

"Field-level change log for one Issue" states a specific verb-plus-resource, and the parenthetical enumerates exactly what the log contains (status, severity, owner, resolution). Naming get_task_history as the clone and implying contrast with get_issue (current state) lets an agent separate it from siblings without opening a schema.

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 before updating an issue another agent may have touched" gives a concrete trigger condition, which is unusually actionable for a read tool. It stops short of naming the alternative reads (get_issue, list_issues) for the case where no conflict check is needed, so it is clear context without full when/when-not coverage.

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