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

readOnlyHint=true is already declared in annotations, and the trailing "Read-only." merely repeats it. The description does add useful context that returned jobs carry status and timing and that only platform jobs (create/update/reconcile) are included, but says nothing about ordering, retention window or result volume.

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 sentences, front-loaded with what is returned and followed by the purpose statement. The final "Read-only." is redundant with the annotation and is the only wasted clause.

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?

With no output schema, the description usefully sketches the shape of results (job type, status, timing) and the schema covers pagination fully. It is close to complete, though result ordering and any time-window limits remain unstated.

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%, so application_id, page and page_size are all documented in the schema, including defaults and the max of 100. The description adds no parameter meaning beyond that, so the baseline of 3 applies.

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?

States a specific verb and resource (get an Application's platform job history) and the parenthetical enumerates the job kinds (create/update/reconcile) with status and timing, which distinguishes it from get_jobs and get_application_workflow_run_jobs. It stops short of naming any sibling, so an agent must still infer which job-oriented tool to pick.

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 to see what the platform has been doing to the application" gives a loose usage context but no exclusions or alternatives. Near-identical siblings such as get_application_workflow_run_jobs, get_application_timeline and get_application_deployments are never mentioned, so the agent gets no routing help.

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