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

With no annotations, the description carries the full burden of disclosing behavior. It mentions billing ('Billing per call: 1 Credits') but does not reveal whether this is read-only, what the response shape is, or if there are any side effects or limitations. The read-only nature is assumed from the GET-style name, but not explicitly stated, and no other behavioral traits are disclosed.

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 sentence, which is concise, but it contains a typo ('comanies') and an unnecessary 'Group: Companies' fragment that adds noise. The billing note is useful, but the overall structure feels rushed and unpolished.

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 list endpoint, the description is incomplete. It does not mention pagination, response format, or any filtering beyond company IDs. With no output schema and no annotations, the agent is left without key operational details, making the description insufficient for fully safe and correct invocation.

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 only 50% (only companyIDs has a description). The description reinforces that companyIDs are IDs, but it does not clarify the 'start' parameter, which likely relates to pagination or offset. The description adds minimal value beyond the schema and does not compensate for the undocumented parameter.

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: 'get available jobs for given companies by ID'. It identifies the resource (jobs) and the scope (by company IDs), which is sufficiently specific. However, it does not explicitly distinguish this from sibling tools like get_api_v1_jobs_search, which also deals with jobs, but the company-ID scoping does provide some differentiation.

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 provides no guidance on when to use this tool versus alternatives such as get_api_v1_jobs_search or get_api_v1_companies_company_posts. There is no mention of use cases, prerequisites, or exclusions, leaving the agent to infer usage context from the tool name and sibling list.

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