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

Annotations already indicate a non-read-only, non-idempotent write; the description aligns with that and adds the destination ('Kanban tracker board'). It does not disclose consequences like duplicate entries on repeat calls or whether an existing application can be updated, so it adds limited behavioral context beyond annotations.

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?

Single sentence, grammatically direct, with no filler. It front-loads the action before the destination, and nothing needs to be cut or rearranged.

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 6-parameter create-style write tool with full schema documentation, annotations, and an output schema, the core invocation contract is clear. It lacks explicit when-to-use guidance and duplicate/update behavior, but these are not fatal given the schema and sibling list.

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?

The input schema provides 100% descriptions for all six parameters, so the baseline applies. The description adds no meaning about company_name, job_title, or status beyond what the schema already documents.

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?

Clearly states a specific action ('Record') and resource ('job application') plus destination ('Civify Kanban tracker board'), which distinguishes it from civify_list_applications and other CV/candidate siblings. The title 'Track' is clarified by the description.

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?

No statement of when to use this tool or when to prefer an alternative. It never mentions civify_list_applications for viewing existing applications or conditions such as having a logged-in account or API key. The only context is the destination board, which implies but does not explain usage.

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