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

Annotations already mark this as read-only and non-destructive, so the safety profile is covered. The description goes further by disclosing exact response fields (jobOpen, isWithdrawable), the limitation that pipeline stages are not tracked, and the nuance that applications with isWithdrawable=false can still be withdrawn via email but not MCP. No annotations are contradicted.

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 description is efficiently front-loaded with the core purpose, then adds high-value behavioral details in compact sentences. Every sentence earns its place: fields returned, withdrawability semantics, email caveat, and pipeline-stage limitation. There is no filler or repetition.

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?

The tool is simple (one optional parameter) and has a rich output schema, so the description does not need to explain return values. It covers ordering, pagination, field semantics, edge behavior around withdrawal, and explicitly states a limitation. An agent has everything needed to select and invoke it correctly.

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 coverage is 100%, and the single page parameter is fully described in the schema with type, default, minimum, and meaning. The description's mention of pagination adds context but does not introduce parameter semantics beyond the schema, 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?

The description opens with a specific verb and resource: 'List your submitted job applications,' and adds ordering ('most recent first') and pagination. It clearly differentiates from sibling tools like search_jobs and get_my_profile by focusing on applications, and it references withdraw_application as a related but distinct operation.

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?

The description clearly indicates this tool is for listing your own submitted applications. It also provides situational guidance around isWithdrawable, telling the agent when an application can or cannot be withdrawn via the withdraw_application tool. It does not explicitly name alternatives for listing applications, but no sibling directly competes, so the context is sufficient.

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