activate-top-candidates

Draft Candidate Pitch

draft_candidate_pitch

Draft a value-first candidate endorsement for review, using a generic role description to highlight public role outcomes without inventing experience or sending messages.

Instructions

Draft a short, value-first candidate endorsement for the sender to review. Pass a generic roleDescription with no client name. The draft leads with outcomes tied to the public role title and never invents experience. It never includes pay or bill rates. Returns a DRAFT only; this tool sends nothing.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "name": "<name>",
      "role": "<role>",
      "roleDescription": "<roleDescription>"
    },
    "name": "draft_candidate_pitch"
  }
}

Input Schema

Name	Required	Description
`id`	No
`url`	No
`name`	Yes	Public name (first name + last initial)
`role`	Yes	Public role title
`category`	No	Category slug or name
`roleDescription`	Yes	Generic role description (no client names)

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Oct 16, 2026

TDQS

A4/5.0

Behavior4/5

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

With no annotations, the description carries the full behavioral burden and does so well: it states the tool never invents experience, never includes pay/bill rates, and crucially that it 'Returns a DRAFT only; this tool sends nothing.' It does not cover permissions or rate limits, keeping it short of a 5.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Six tight clauses, no waste, and the core purpose is front-loaded in the first sentence. Each subsequent sentence adds a distinct, non-redundant guardrail (input form, content constraints, output nature).

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema, the description correctly compensates by stating what is returned ('a DRAFT only; sends nothing'). It covers the key behavioral guardrails for a 6-param generation tool but omits how id/url/category influence the draft and any auth or rate-limit context.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 67%, and the one parameter the description highlights (roleDescription as generic with no client name) is already documented in the schema itself, so it adds little. The other parameters (id, url, category) receive no explanation in either the schema or the description. Baseline 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a specific verb (Draft) and resource (candidate endorsement/pitch) and immediately qualifies the output as 'short, value-first' and 'for the sender to review.' This clearly separates it from all siblings, which are retrieval/match tools (search_top_candidates, match_role, get_candidate_link), so there is no plausible tool confusion.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives usage conditions ('Pass a generic roleDescription with no client name') and content guardrails, which implies when the tool is appropriate. However, it never explicitly states when to use this tool versus an alternative, nor names any sibling, leaving the routing decision to inference.

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

Deploy Server