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

The description adds genuinely load-bearing semantics beyond the annotations: it defines what the 'completed' status actually means ('it was submitted') and reveals the payload shape (status, filled fields, live view link). The readOnlyHint=false on a tool called 'Check' is not explained, but the added status semantics and return contents are real value.

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?

Two short sentences, front-loaded with the domain and action, then the status semantics. Nothing is padded or repeated from the title or schema.

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?

An output schema exists, so return values need not be explained, yet the description helpfully summarizes them and clarifies the ambiguous 'completed' status. Gaps remain around failure modes (invalid or expired session_id) and whether repeated calls have side effects given readOnlyHint=false.

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 0% and session_id is never mentioned in the description, so the parameter's meaning and header-based passing are undocumented there. The description does at least frame the call as targeting one application (session-scoped), which partially compensates, but a 3 is the ceiling for a fully undocumented identifier.

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 pairs a specific verb ('Check') with a specific resource ('an application Worklittle is filling out') and even enumerates the returned data (status, filled form fields, live view link). It distinguishes itself implicitly from the listing sibling (list_active_applications) by scoping to a single application, though it never names an alternative explicitly.

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?

There is no explicit when-to-use or when-not-to-use guidance, and no sibling tool is named (list_active_applications, apply_for_job, track_applied_job all sit nearby). The phrase 'an application Worklittle is filling out' implies the context of an in-progress application, but the agent must infer that alone.

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