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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety is covered. The description adds genuinely new behavioral context by disclosing what the payload contains — the complete description and how to apply (apply link, HR email, or WhatsApp depending on the employer) — which matters since there is no output schema.

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 compact sentences, front-loaded with the action and scope, then the input source. Every clause carries information; nothing is padding.

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 single required parameter with full schema coverage and annotations covering the safety profile, the description fills the main remaining gap by describing return content in the absence of an output schema. It does not mention failure behavior for an invalid or expired slug, a minor omission.

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 description coverage is 100% and the slug field already documents both the example slug and the full-link alternative, so the description largely restates it. The mention that the slug comes from search_jobs adds a small amount of provenance context but no new format or constraint detail.

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 ('Fetch one Indian listing in full') with the scope narrowed to a single record, which cleanly separates it from search_jobs and search_global_jobs. It even names what 'full' means (description plus application method), so the agent knows exactly what it gets.

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?

Gives clear context for invocation: the slug 'Takes the slug from search_jobs, or a carrerlift.in/jobs/ link', which chains this tool after the search tool and tolerates two input shapes. It stops short of explicit when-not-to-use guidance or naming alternative detail-fetch paths.

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