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

Annotations already declare readOnlyHint=true and idempotentHint=true, so the tool is known to be safe. The description adds transparency by enumerating exactly what data is returned (company, title, stage, outcome, when sent, number of pending screening questions, employer acknowledgement). This goes beyond the schema and gives the agent a clear picture of the response, though it doesn't discuss pagination or other edge behaviors.

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 compact and front-loaded with usage triggers ('what did I apply to'), followed by a specific list of returned fields. Every sentence earns its place, with 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 there is no output schema, the description does a good job enumerating the return fields. It covers the essential information an agent needs to understand what the tool returns. However, it does not mention how 'limit' or 'include_cover_letter' affect output, nor does it describe ordering or default behavior, leaving minor gaps in completeness.

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 only 33%, with only 'only_waiting_on_me' documented. The description does not mention 'limit' or 'include_cover_letter' at all, and provides no guidance on how these parameters affect results. With low schema coverage, the description should compensate, but it fails to do so, leaving the agent without semantic clarity for two of three params.

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 states a clear purpose: listing all applications sent for the account, with a specific resource (applications) and specific output fields (company, title, stage, outcome, etc.). It also gives example user queries that directly map to the tool, distinguishing it from siblings like get_tracker or explain_job_match.

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 explicit example use cases ('what did I apply to', 'any replies', 'status of my applications'), which clearly indicate when to use this tool. However, it does not explicitly mention when not to use it or name alternative siblings, so it lacks the 'when-not' component of a top score.

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