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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description adds meaningful behavior beyond that: the pagination warning (list may span multiple pages) and the default status behavior (open). Also clarifies that 'all of which is public record' – i.e., no access control concerns. This is genuinely useful behavioral context.

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, front-loaded with purpose, then defaults and a behavioral caveat. Zero filler, direct and skimmable.

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?

Covers the essential call context: what job type you get (all statuses), defaults, and pagination. Lacks an explicit note about output shape (no schema provided), but for a list operation the pagination hint effectively covers the main gotcha. Could mention the sort parameter's interaction with limiting but that's minor. Slightly below 5 because it doesn't hint at what 'list' means in terms of fields returned.

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 covers all parameters at 100% with enums. The description adds clarity on sort semantics ('shortest_first' by ascending days, 'highest_rated' is poster's rating) and corrects the limit maximum to 100 (schema allows a huge range but description states actual cap). This is meaningful added value, though a score of 5 would require even closer tie-in of every parameter to behavior.

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 ('List'), the resource ('jobs'), and the platform ('Freelance Clearing'), and implicitly distinguishes itself from single-job and own-job siblings. The default-to-open framing removes ambiguity about which subset the tool returns.

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: defaults to open jobs (bid-able), status parameter to reach other work, and warns to read the pagination block. Does not explicitly name sibling alternatives like get_job or get_my_jobs, but the wording 'all of which is public record' implies the range of statuses. Slight deduction for not naming siblings.

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