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

Annotations already declare readOnly/idempotent/non-destructive/closed-world. The description adds genuinely new context beyond them: the data is illustrative demo data and applications are closed, which materially affects how an agent should interpret and present results.

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?

Front-loaded two-fragment description with no filler; every clause carries information about the tool's nature and output content.

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 read-only, no-output-schema tool this covers what is returned ('company profile and its roles') and the demo caveat, but leaves the one required parameter's provenance and format undefined.

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 slug parameter has 0% schema description coverage, so the description must carry the burden, and it explains nothing about what a slug is, where to obtain one, or whether it accepts a company ID or name.

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 ('Read') and resource ('sample company profile and its roles'), and the 'Demo catalog' framing distinguishes it from production siblings like get_published_company.

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?

'Demo catalog: illustrative roles, applications closed' implies this is for demo/sample scenarios, but it never states explicitly when to choose this over get_published_company or demo_get_job, nor where a valid slug comes from (likely demo_list_companies).

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