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

Annotations declare readOnlyHint=true, so the description need not restate safety. It adds meaningful behavioral context: only verified accounts appear, sorting/filtering is user-driven and not a ranking, and the platform publishes the figures. These details go beyond the annotation and help the agent understand output semantics.

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?

The description is well-structured, starting with the core purpose, then listing data fields, and ending with use-case rationale. It is somewhat verbose but every sentence adds value—no filler. It is front-loaded with the most important information and remains scannable.

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 read-only list tool with 5 fully documented parameters and no output schema, the description explains the returned fields (username, rating, job counts, earnings) and the intended use case. It does not mention pagination explicitly, but the offset parameter description covers that. The tool is sufficiently specified for an agent to invoke correctly.

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 schema already documents every parameter thoroughly. The description adds only a high-level note that sorting/filtering is flexible, but it does not elaborate on parameter-specific behaviors like the meaning of '4up' or the default sort. Baseline 3 is appropriate given the schema's completeness.

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 the verb 'list' and the resource 'people on Freelance Clearing', explicitly equating it to the Users tab. It differentiates from sibling tools like browse_jobs by explaining it is the only way to start from a person rather than a job, making its unique purpose unambiguous.

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?

The description gives explicit when-to-use guidance: 'Use it to find someone to hire when you have no job to start from, which is otherwise impossible.' It also contrasts this with the alternative of finding a job first, clearly indicating when this tool is preferred over job-oriented searches.

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