get-my-jobs

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

No annotations provided, so the description must disclose behavioral traits. It only states 'active' jobs, but does not mention pagination, rate limits, authentication requirements, or side effects. The read-only nature is implied but not explicit, leaving uncertainty.

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?

Single sentence with no superfluous words. However, it could be slightly more detailed without becoming verbose. The information is front-loaded but minimal.

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?

Despite full schema coverage for parameters, the description lacks details on return value, pagination behavior, and definition of 'active'. Without an output schema, more context would help. It is adequate for a simple list tool but leaves gaps.

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 100%, with both 'page' and 'perPage' already defined in the schema with clear descriptions. The tool description adds no additional meaning beyond what the schema provides. Baseline 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?

Description clearly states verb (List), resource (job vacancies), and scope (active). It is specific enough to understand the tool's purpose. However, it does not explicitly distinguish from siblings like 'get-my-bookings' or 'post-job', but the name and description suggest a narrow focus.

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. The description does not mention scenarios where this tool is appropriate or when to use sibling tools like 'get-my-bookings' or 'post-job'. Implicitly, it is for listing the user's own active jobs, but no explicit context.

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