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

Annotations already cover the read-only, idempotent, non-destructive profile, so the description correctly focuses on data semantics instead: pending-review jobs are included, invite links are stripped, and applied jobs are absent with a reason given. That is meaningful context beyond the annotations. It stops short of describing ordering, pagination, or what happens when `role` is set to 'applied'.

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 primary scope before the exclusions, with no filler. The final clause about the poster account is slightly cryptic but earns its place as the justification for the exclusion.

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 two-parameter list tool with no output schema, the description covers inclusion and exclusion but leaves the return shape, ordering, and the meaning of `role`/`limit` unexplained. The unresolved tension between the stated exclusion and the 'applied' enum value is a real completeness gap.

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%, so the description carries the full burden for `role` and `limit` and largely fails. It never explains the `role` enum values and actually contradicts the 'applied' option by asserting applied jobs are not listed, and it says nothing about the `limit` bound or default. The one sentence it does spend on applications raises more questions than it answers.

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 states a specific resource (jobs) and a clear scope (posted by the signed-in user), which separates it from the broader list_jobs sibling even though it never names that sibling. An agent can tell what it returns without opening the 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?

It gives one useful exclusion (applied jobs are not listed), which implies when to pick list_my_jobs over an application-oriented path. But there is no explicit routing to list_jobs or get_application_status, and the stated exclusion directly conflicts with the `role` enum that offers 'applied', leaving the agent unsure which source of truth to trust.

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