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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds nothing behavioral—no mention of required identifiers, authentication, or whether the posting is live/archived—so it contributes only the bare noun phrase.

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 fragment rather than a front-loaded sentence. Its brevity reflects under-specification, not efficient conciseness—there is no structure to speak of and no key information is conveyed.

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 detail-fetch tool requiring two undocumented parameters, the description is completely inadequate. Although an output schema and annotations exist (reducing the need to describe return values and safety), the 0% parameter coverage and absent usage context mean an agent cannot reliably call this tool.

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?

Schema description coverage is 0% for two required parameters (id, company), and the description mentions neither. It provides no meaning for what 'company' should be (slug, name, ID) or how 'id' relates to it, leaving the agent unable to infer parameter values.

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 'Single SmartRecruiters posting.' is a noun phrase that essentially restates the tool name (jobs_smartrecruiters_posting), supplying no action verb. It only hints at the singular-vs-list distinction already implied by the name and the sibling jobs_smartrecruiters_postings. This is close to tautology rather than a clear statement of what the tool does.

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?

No guidance is given on when to use this tool versus the plural sibling jobs_smartrecruiters_postings, nor are any prerequisites or contexts described. The word 'Single' hints at individual-record retrieval but is not an explicit usage instruction.

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