get_company_jobs

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

No annotations and no behavioral information in the description (e.g., destructive/read-only, authentication needs, rate limits); the agent has no insights into side effects.

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-word description is extremely terse but merely repeats the tool name, adding no new information and failing to earn its place.

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?

Given zero parameters, no output schema, and many sibling tools, the description provides no contextual guidance on prerequisite state (e.g., company context) or expected output, leaving the agent underinformed.

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?

Input schema has zero parameters with 100% coverage, so description adds no parameter-level detail; baseline 3 is appropriate as the schema already fully documents the lack of parameters.

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?

Description 'Get company jobs' is vague; it doesn't specify what it returns (list/details) or how the company is identified, and fails to differentiate from sibling tools like search_jobs or get_company_details.

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 on when to use this tool versus alternatives such as search_jobs or get_job_details, leaving the agent without context for selection.

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