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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so safety and idempotency are covered. The description adds that every status bucket is returned and points to a `say` summary field, which is useful behavioral context, but says nothing about ordering, emptiness, or payload shape.

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 the resource definition. Every sentence carries content: resource, scope of statuses, and the summary field pointer. Minor room to tighten the status enumeration.

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 zero-param read tool with annotations, the description largely suffices, and the `say` pointer partially substitutes for a missing output schema. However, without an output schema it does not explain the returned structure beyond status buckets, leaving the consumer to guess the shape.

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?

There are zero parameters, so there is no parameter meaning to convey; baseline 4 applies. The description adds nothing to compensate for, and no parameter information is missing.

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 resource - the person's job board - and enumerates the statuses it covers (saved, preparing, applied, interview, offer), which distinguishes it from single-item tools like get_application. The verb is implicit (retrieve) rather than explicit, but the resource and scope are clear enough to separate it from siblings.

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?

No guidance on when to use get_tracker versus list_applications, get_application, jobs_for_me, or move_on_tracker. The mention that a summary lives in `say` hints at a consumption pattern but offers no when/when-not routing.

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