save_job_posting

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

No annotations exist, so the description must fully disclose behavior. It states it fetches/saves but does not explain what 'save' entails (side effects, storage location), error behavior for conflicting inputs, or mention the workspace_dir parameter. Significant gaps remain.

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 concise with two sentences and a bullet list. It is front-loaded with purpose. The bullet list could be more structured, but it efficiently conveys key information without waste.

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 having an output schema, the description misses the workspace_dir parameter, provides no context on 'save' behavior, and lacks guidance on when to use this tool. For a tool with 4 parameters and no annotations, this is incomplete.

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 coverage is 0%, so the description must add meaning. It explains company, url, content, and notes mutual exclusivity of url and content. However, it omits workspace_dir entirely, and the explanations are brief, lacking types or examples.

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 fetches a URL or accepts text and saves it for a company. The verb 'save' and resource 'job posting' are specific, but it does not explicitly distinguish from sibling tools like fetch_url or save_application_file.

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 a clear usage rule: provide url or content, not both. However, it does not mention when to use this tool over alternatives (e.g., fetch_url for just fetching, or when not to use it).

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