Score Job

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

With no annotations, the description carries the full burden of behavioral disclosure. It does not say whether scoring persists state, what side effects occur, what the returned score represents, or whether any preconditions (e.g., a verified master resume must already exist) are required. 'Score... against' names the behavior but leaves important traits unspecified.

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 front-loaded sentence with no filler or repetition. Every word—'Score', 'one job', 'verified master resume'—contributes to the operative meaning.

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?

The presence of an output schema reduces the need to explain return values, and the input schema defines the shape of the job. However, the description still omits whether a master resume must be prepared beforehand, whether the score is saved anywhere, and what distinguishes this from assess_submission, so it is only minimally complete.

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 schema's description coverage is 0%, and the description adds no parameter-specific meaning. Although property names (company, role, description, job_url, location, sponsorship) are somewhat self-explanatory and the required fields are visible, the description does not compensate for the lack of schema documentation.

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?

Description states a specific action ('Score') on a specific object ('one job') and adds the distinctive reference point ('verified master resume'). It is clear and meaningfully distinct from siblings like search_jobs and tailor_resume; however, it does not explicitly differentiate itself from assess_submission or save_application_snapshot.

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?

'Score one job against the verified master resume' implies this tool is for evaluating a single job posting against the stored master resume, but it gives no explicit when-to-use/when-not-to-use guidance or alternative sibling recommendation. Usage is inferable, not stated.

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