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

With no annotations, the description must convey safety and behavior. 'Fetch' implies a read operation, but it does not explicitly state that it is safe, non-mutating, or what happens on errors. It also omits any authentication or permission expectations. For a simple getter, this is adequate but lacks explicit disclosure.

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, efficient sentence that communicates the core action without any filler. It is well-structured and easy to parse.

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 simple fetch-by-id tool with a single parameter and no output schema, the description provides sufficient context: it identifies the resource and the lookup key. It does not explicitly describe the return structure, but 'assessment' implies the content. It is complete for the tool's simplicity.

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 fully documents the single parameter (assessment_id) as the id returned by assess_job_description. The description merely reiterates 'by id' without adding format, range, or usage nuances. With 100% schema coverage, this meets the baseline but adds no extra value.

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 clearly states the action (fetch), the resource (a previously run job-description assessment), and the unique identifier (by id). It unambiguously distinguishes from siblings like list_my_assessments (which lists) and assess_job_description (which creates).

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 description implies the tool retrieves a single past assessment, but it does not explicitly state when to prefer this over alternatives like list_my_assessments or check_role_status. There is no mention of exclusions or selection criteria, leaving usage largely implied.

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