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

Annotations already declare readOnlyHint=true and openWorldHint=false, and the description layers on genuinely new operational constraints the annotations do not carry: a hard cap of 5 upwork_id per call and a throttle of 30 jobs per hour. Disclosing rate limits and batch ceilings is precisely the context annotations cannot convey.

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?

Three compact sentences, front-loaded with what data is returned, then when to use it, then operational limits. The field enumeration is long but each item is informative; no filler or repetition.

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?

With no output schema, the description still tells the agent what comes back, where the input IDs must come from, when the tool is appropriate, and the rate/batch limits. Nothing an agent needs in order to invoke it correctly is missing.

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%, so the single parameter and its 1-5 array bounds are already fully documented in the schema, establishing the baseline of 3. The description restates the 'Up to 5 upwork_id per call' bound and the find_jobs provenance, which is mildly reinforcing but adds no new syntax or format meaning.

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+resource ('Full data of jobs') and enumerates exactly what the payload contains (experience level, duration, workload, category, client statistics). It explicitly positions itself relative to the sibling find_jobs by scoping to jobs that tool already returned, so an agent can distinguish the two without opening a 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?

Gives an explicit positive condition ('Only for jobs already shortlisted by title, description and skills, when the user needs more to decide') and an explicit exclusion ('never for every job found'). The routing rule between find_jobs and get_job_details is unambiguous.

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