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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is fully covered by structured data. The description adds nothing beyond noting that describe_operation carries the native request schema — mildly useful given the odd query/params envelope, but no disclosure of pagination, result shape, or scope of the history returned.

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 text is short but the first two sentences are an exact duplicate of each other, wasting half the description on repetition. The content is front-loaded but the payload is essentially zero; the operation ID and boilerplate referral consume the remaining space.

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 nested-object, two-parameter history endpoint with no output schema and no parameter documentation, the definition leaves the agent unable to construct a valid call without first invoking describe_operation. Nothing about result contents, filtering, or paging is provided, so the definition is incomplete relative to the tool's complexity.

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% for two parameters (an open-ended 'query' object and an empty 'params' object with additionalProperties=false), and the description supplies no meaning for either. The delegation to describe_operation is the only clue, so an agent cannot tell from this definition what to put in 'query' or why 'params' accepts nothing.

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 only repeats the HTTP path 'GET /api/ai/find-changes/history' twice, which is a restatement of the title rather than an explanation of the tool's purpose. From the path an agent can infer it retrieves history for AI find-changes runs, but nothing states what a 'run' is, what the history entries contain, or how it differs from the sibling get_ai_find_changes_history_by_runId_1124444e3a0f40ff6090965f.

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?

There is no when-to-use guidance, no exclusions, and no mention of the obvious alternative (the by-runId history sibling). The only actionable instruction is a pointer to describe_operation for native request schemas, which addresses schema discovery rather than tool selection.

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