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

Annotations already declare readOnlyHint/idempotentHint/destructiveHint=false, so the safety profile is covered elsewhere. The description adds nothing beyond that — no pagination, no filtering behavior, no indication of what the job list contains or its state lifecycle.

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?

Very short, but the first sentence is the endpoint path stated twice, which is pure redundancy, and the useful part (the describe_operation pointer) is buried at the end. It is brief by omission, not by efficiency.

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 tool with a nested/free-form query object, 0% schema coverage, and no output schema, an agent gets essentially no information needed to invoke it correctly beyond the method and path. The description should at least explain what query fields or job states are accepted.

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% and the two parameters (a free-form 'query' object and an empty 'params') are completely undocumented. The description does not compensate at all; the only clue is a generic redirect to describe_operation for the real request schema.

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 is just the endpoint path repeated twice with an operation ID; it restates the name rather than saying what a 'full-abstract changes job' is or returns. It never distinguishes this from the sibling get_ai_find_changes_full_abstract_by_jo_... which presumably fetches one job by id.

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 statement of when to call this versus describe_operation, execute_read, or the by-jobId sibling. The only procedural hint is a generic pointer that describe_operation provides native schemas.

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