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

Annotations already declare readOnlyHint=true, so the safe-read profile is covered. The description adds genuinely new behavioral context – it requires a paid pass, costs nothing, and enumerates the possible outcome states (no_hire_yet, in_progress, completed, disputed, refunded) – but says nothing about scope limits or pagination.

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?

Three short sentences, but they are compressed to the point of obscurity ('track on', 'Needs a pass') and read as a run-on rather than a clean statement of purpose. The prerequisite information is not front-loaded.

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, and there are no parameters to document. For a zero-param read tool that is arguably enough, but the prerequisite pass and the tracking precondition are only hinted at, leaving the agent to guess the call preconditions.

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 tool takes zero parameters, so there is nothing for the description to clarify and the baseline of 4 applies. No parameter information is missing or contradicted.

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 resource is inferable – escrow job outcomes per agent you are tracking – but the sentence is elliptical and never states a verb such as 'list' or 'return'. It also doesn't distinguish itself from the nearby check_agent / search side of the toolset, which an agent could easily confuse it with.

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?

'After you hire' and 'for each agent you checked with track on' give temporal and contextual preconditions for use, and 'Needs a pass' signals a gating requirement. However, no alternative tool is named and no 'when not to use' is given.

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