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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so the safety profile needs no explanation. The description adds real value beyond them by disclosing the return payload (full record plus an assessment rubric that includes gaps) — significant given no output schema exists.

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 sentences, both load-bearing: the first is the invocation trigger front-loaded at the very start, the second is the return-value contract. No filler or restatement of the name or title.

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?

For a single-parameter read tool with no output schema, the description supplies both the trigger and the shape of the response (record + rubric + gaps), which is what an agent needs to route the call and interpret it. Minor gap: 'complete record' does not specify which record, though siblings imply a candidate profile.

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 single parameter has 100% schema description coverage ('The job description or role summary'), so the schema does the work. The description references job descriptions but adds no format, length, or content guidance beyond what is already structured. Baseline 3 for full schema coverage.

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?

States a specific verb and resource ('Evaluate fit for a role', 'fit assessment') and, crucially, names what it returns that siblings do not: 'his complete record and a rubric.' An agent can distinguish this from get_profile or get_skills_with_evidence without opening any schema.

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 opening clause gives an explicit trigger condition: 'Call when the user shares a job description or asks whether Anto fits a role.' That is clear context for invocation, but no when-not guidance or alternatives (e.g. get_profile for a plain lookup) are offered.

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