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

Annotations already declare readOnly, idempotent and non-destructive, so safety is covered. The description adds genuinely useful behavioral context beyond them: the call returns a company profile as well as the posting, and applications on the demo record are closed. It says nothing about lookup failure behavior for a missing slug.

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 short sentences, zero filler, and the resource is front-loaded before the caveat. Tight enough that nothing needs cutting, though it is arguably too terse given the undocumented parameter.

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 single-parameter read tool with annotations covering its safety profile and no output schema, the description covers return content adequately. The unexplained slug parameter is the main gap, leaving it minimally viable rather than 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?

Schema description coverage is 0% — 'slug' has only a type and maxLength, no description. The description does not compensate at all: it never explains what the slug identifies, where it comes from, or what happens on an unknown 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?

States a concrete verb and resource: reads a job description plus its company profile, with the 'demo' qualifier flagging the dataset. It is distinguishable from get_company and search_jobs, but never names or contrasts with close siblings such as check_job_posting or list_company_openings.

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 when-to-use guidance and no alternative named. 'Applications are closed' is a domain caveat, not a routing condition, so an agent gets no help deciding between this and check_job_posting or list_company_openings.

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