get_company_jobs

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

No annotations are provided, so the description must carry the full burden. It only states the action 'List' without disclosing additional behavior such as pagination, error handling, or response format. Since there is no readOnlyHint annotation, the agent must infer safety from the word 'List'.

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 two sentences, with the purpose first and a clearly formatted Args section. Every word adds value; the example is concise and directly relevant to the parameter.

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 tool with a single required parameter and an output schema, the description covers the essential input semantics well. However, it lacks any context about when to choose this tool over its siblings, making it slightly incomplete for an agent deciding between tools.

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 input schema only specifies `company` as a string with no description. The description adds critical details: 'The company's XING page slug or full page URL — the part after /pages/, e.g. "exxetaag" for xing.com/pages/exxetaag.' This gives the exact format and an example, far exceeding the schema's empty description.

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 tool's function: 'List the open positions published on a company's XING page.' This uses a specific verb ('List') and a specific resource (jobs on a company's page), distinguishing it from siblings like `get_job_details` (specific job) and `search_jobs` (global search).

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 implies usage for retrieving jobs from a specific company page via the `company` parameter, but it does not explicitly mention when to prefer alternatives like `search_jobs` for cross-company searches. This leaves usage context partially implicit.

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