apply_resolve_source

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

The description states 'No network calls are made' which is a useful behavioral hint. However, with zero annotations, it should also disclose any destructive action, auth requirements, or side effects. Lacks details on error handling or edge cases.

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?

Two sentences that are concise and front-loaded. Every sentence adds value without redundancy.

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?

Given the complexity of the nested object and the presence of an output schema (not shown but existence indicated), the description covers core functionality and principle. However, it omits mention of required fields within the job object or what the output shape is.

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 describes the 'job' parameter as 'A normalised JobPosting' but nested properties lack descriptions. The tool description adds no additional parameter-level semantics 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 clearly states it resolves the best apply URL and channel, and explains the apply-at-source principle. It is specific about its function but does not explicitly differentiate from sibling tools like apply_act or source 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?

No guidance on when to use or when to avoid this tool. No mention of alternatives or prerequisites, even though siblings exist (e.g., source tools for fetching jobs, apply tools for actual application).

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