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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description adds the context that the data comes from the candidate's Civify Kanban board, which is useful. However, it doesn't disclose return format, pagination, or whether the list is ordered, but with annotations covering the core behavioral traits, a 3 is appropriate.

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 a single, clear sentence with no wasted words. It front-loads the action ('List') and the resource ('tracked job applications'), and the source ('Civify Kanban board') is included efficiently.

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 simple read-only list tool with one optional parameter and a full output schema, the description is nearly complete. It could mention that the list is from the candidate's own board, but that's already implied by 'candidate's Civify Kanban board.' The annotations cover safety, and the output schema covers return values, so nothing critical is missing.

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%: the only parameter, api_key, is described as 'Optional API key override.' The description adds no additional parameter semantics beyond what the schema already provides. Baseline 3 is correct when the schema fully documents the parameter.

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 verb 'List' and the resource 'tracked job applications' from the candidate's Civify Kanban board. It distinguishes itself from siblings like civify_track_application (which adds an application) and civify_get_account (which retrieves account info), though it doesn't explicitly name alternatives.

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 implies usage context: it lists tracked applications from the Kanban board, so an agent can infer it's for reading the candidate's application tracking data. However, it doesn't explicitly state when to use this tool versus alternatives like civify_track_application or civify_get_account, nor does it mention any exclusions or prerequisites.

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