Add application

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

Annotations declare a non-destructive write that is not open-world; the description usefully adds that the record persists locally on this machine, that status defaults to "applied", and that an id comes back. It does not say what happens on duplicates or invalid deadlines, which would round out behavior for a write tool.

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?

Front-loaded with what the tool does and its default behavior, followed by inputs and a concrete example. The input enumeration is somewhat redundant against the schema but stays a single efficient paragraph; the example prompt earns its space by showing combined usage.

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 annotations, full schema coverage, and an output schema, the description covers everything an agent needs to call this correctly, including the id return value that downstream tools depend on. Missing only edge-case behavior (duplicate entries, deadline format validation) for a fully complete picture.

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%, so all seven parameters and both enums are already documented in structured form. The description mostly restates that content (required company/role, YYYY-MM-DD deadline, source examples) rather than adding semantics the schema lacks, so baseline 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 ("Add a job or internship to the tracker") and immediately clarifies default placement in the applied stage. It also names a downstream consumer ("returns its id, which update_status needs"), which distinguishes it from the sibling tools that read or change existing entries.

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 sequencing hint (the returned id is required by update_status) tells the agent where this fits relative to alternatives, and the worked example prompt anchors realistic usage. It stops short of explicit "do not use this for X" exclusions, but the create-vs-update boundary is implied clearly enough.

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