Get job details

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

No annotations are provided, so the description carries the behavioral disclosure burden. It adds 'API-only' as a behavioral trait and names the returned fields, but it does not mention edge cases such as not-found behavior, authentication, or response shape beyond the listed fields.

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 one concise sentence that front-loads the main action, specifies the lookup key, and lists relevant return fields. Every part adds value with no repetition or filler.

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 single-parameter lookup tool, the description provides enough context to call it correctly: the operation, the identifier format, and the expected returned fields. The absence of an output schema is partially compensated by listing the key returned data.

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 already documents jobId as 'Work at a Startup job ID' with 100% coverage. The description reinforces this with 'WAAS jobId' but does not add meaningful detail beyond the schema.

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 states a specific verb ('Get'), a specific resource ('detailed job info'), and an exact lookup key ('WAAS jobId'). It also lists the kind of information returned (description, tags, salary), which helps distinguish this direct-fetch tool from the sibling search tools.

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 clearly implies this is the tool to use when you already have a WAAS jobId and need detailed information. It does not explicitly name alternatives or exclusions, but the context of a single required jobId parameter makes the intended usage clear.

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