Track Application

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

With no annotations, the description carries the behavioral burden. It usefully discloses that this is a tracking action, not a submission action, which prevents a meaningful misuse. However, it does not explain what happens on duplicate entries, whether the action is reversible, or any persistence/confirmation behavior, so transparency is adequate but not rich.

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, purposeful sentences. The core action is front-loaded, the key non-behavior is stated immediately after, and the jd_text guidance is concise but meaningfully explained. No filler or redundancy.

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?

Given the output schema exists and the input schema covers all parameters, the description covers the important contextual gaps: what the tool does, what it does not do, and when to include jd_text. It could add a note about duplicate handling or status defaults, but the schema already documents the status default, so the remaining context is reasonably complete.

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 the baseline is met. The description adds extra semantic value to jd_text by explaining why storing it matters ('tailor their CV against the real requirements later'), which goes beyond the schema's simple 'pasted in full' description. Other parameters are already well documented in the 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 uses a specific action verb and resource ('Add a role to the application pipeline') and explicitly states it 'never submits one,' clearly distinguishing this from submitting or updating applications. This makes the tool's purpose and boundary immediately obvious.

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 frames when to use it: when adding a role to the pipeline. It also gives explicit contextual guidance for jd_text ('Pass jd_text when the user has the posting to hand'), which helps the agent decide on parameter usage. It does not explicitly name sibling alternatives such as update_application, but the addition-versus-update distinction is implied.

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