mbs_jobs

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

With no annotations, the description carries full responsibility for behavioral disclosure. It only says 'List job openings' which implies a read operation, but provides no additional detail on pagination, return format, or any limitations. The description adds little beyond what the tool name suggests.

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, focused sentence that immediately conveys the tool's purpose. It contains no redundant information and is well-structured for quick parsing.

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 listing tool with one parameter and no output schema, the description is minimally viable. It communicates the source and action but omits details about the return value (e.g., fields, format), which could leave an agent uncertain about how to handle the response. It is complete enough for basic use but lacks deeper context.

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 schema fully documents the single 'limit' parameter with a clear description ('Max items (default 20)'). The tool description does not mention the parameter, but since schema coverage is 100%, a baseline score of 3 is appropriate; no additional param information is needed.

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 lists job openings from the MBS jobs page, specifying both the action and the resource. This distinguishes it from sibling tools like mbs_events or mbs_publications, which target different content types.

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 clear context on the source (MBS jobs page) and the action (listing jobs), making it obvious when to use this tool. However, it does not explicitly mention alternatives or situations where it should not be used, so it lacks a full when/when-not statement.

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