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

With no annotations, the description carries the behavioral burden and does add useful context: the empty-list edge case, per-call billing cost, and the presence of jobId in results. It does not discuss authentication, sorting, or full response shape, but for a read-only list endpoint the main behavioral surprises are covered.

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 compact and front-loaded, with the empty-list behavior first, then follow-up routing, then cost. The 'Group: Companies' metadata is somewhat redundant, but no sentence is wasted overall.

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 with no annotations and no output schema, the description covers the important edge case, the downstream detail endpoint, and cost. However, it leaves pagination behavior to the schema and does not describe response items beyond jobId, making it adequate but not fully 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?

All three parameters already have complete schema descriptions, including defaults for count and start and the origin of companyId from /company/search or /company. The description adds no parameter-specific detail beyond the schema, so the baseline score of 3 is appropriate.

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 title and description clearly identify the tool as listing a specific company's open jobs, and the empty-list note reinforces the exact scope. It is easily distinguished from the search and detail siblings, though it does not explicitly name a sibling comparison.

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 provided on when to use this tool instead of alternatives like get_jobs_search or get_company_companyId_posts. The only directional note, using a returned jobId with /jobs/detail/{jobId}, describes a follow-up action rather than a selection criterion.

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