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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world, so the safety profile is covered. The description adds genuine context beyond that: what fields are returned (source and application URLs), what is excluded (no applicant data, no submission), and a data-quality caveat that compensation text is authoritative while absent numeric pay/units are unknown.

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?

Three short sentences, front-loaded with the resource and scope before the caveats. The compensation-authority sentence is slightly tangential to tool selection but earns its place as a data-interpretation rule.

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 adequately conveys what is returned, what is excluded, and how to interpret the compensation field. The only real gap is any guidance on the slug parameter or when to prefer this over get_company.

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?

There is one parameter (slug) with 0% schema description coverage, and the description never mentions it. The schema's regex pattern hints at a URL-style slug, but the description does nothing to compensate for the coverage gap, so an agent gets no added meaning from the prose.

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 ('a real company-published profile and its current published openings'), and the qualifier 'published' implicitly separates it from the sibling get_company. It never names get_company or list_published_companies explicitly, so sibling differentiation is left to inference.

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 scopes the tool ('no applicant data or application submission') and implies usage via 'company-published profile', but gives no explicit when-to-use condition or routing to alternatives such as get_company or list_published_companies. Usage is inferable but not stated.

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