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

Annotations indicate readOnlyHint=false (mutation) and destructiveHint=false. The description adds value by explicitly stating that the tool creates a new application and returns possible-duplicate warnings, which is useful context beyond annotations. No contradictions observed.

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 remarkably concise, using 2-3 sentences to convey purpose, usage modes, and behavioral notes. It is front-loaded with the core action and contains no redundant information. Every sentence earns its place.

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 tool's complexity (19 parameters, no output schema), the description adequately explains the two input modes, mentions required fields, and covers return value behavior. However, it could briefly indicate when to use specific structured fields (e.g., status, url) for completeness, but overall it is sufficient for an agent to use 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?

With 74% schema description coverage, baseline is 3. The description adds significant value by explaining the raw parameter format in detail and indicating that 'company' and 'role' are required in structured mode (despite schema not marking them required). This helps the agent understand usage beyond schema constraints.

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 clearly states the tool's purpose as tracking a new job application. It distinguishes two input modes (raw line or structured fields) and implies the action of creation. The tool name itself is self-explanatory, and the description reinforces it, differentiating it from siblings like update_application or list_applications.

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 provides usage guidance on how to input data (raw vs structured) and what to do on duplicate detection. However, it lacks explicit comparison to sibling tools like update_application for existing entries or list_applications for viewing, so the agent must infer context from the name alone. The guidance is present but not exhaustive.

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