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

Annotations already mark readOnlyHint and openWorldHint, so safety is covered. The description adds useful operational detail: primary transport is Indeed's credential-free GraphQL API with a fallback to the web-page transport, which tells the agent about reliability and auth characteristics.

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?

Reasonably sized and front-loaded with the core purpose, but the standalone 'jk: Indeed job key (16-character hex)' duplicates the schema, and the trailing 'Use indeed_search to retrieve indeed job search' is grammatically awkward.

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?

An output schema exists so return shape needn't be described, and annotations cover the safety profile. The description adds transport and provenance context, leaving little the agent needs that is missing for a single-lookup tool.

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 100% and the single jk parameter is already documented in the schema. The description restates the 16-character hex format but adds nothing beyond the schema baseline.

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?

States a specific verb and resource (returns one Indeed job posting) scoped by its job key, and explicitly names indeed_search as the sibling for searching. An agent can distinguish it from indeed_search without opening either schema.

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?

Directs the agent to indeed_search for search and implies this tool takes a job_key returned from search, giving clear context for when to use it. It stops short of stating an explicit when-not or full prerequisite chain.

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