List freelancers or employers

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

The description is highly transparent about the tool's actual behavior: it returns 404 for regular tokens. This is important operational information that would otherwise be surprising, especially given the readOnlyHint annotation.

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 a single concise sentence that includes both purpose and current behavioral status. It is well-structured and contains no unnecessary words.

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 simple listing tool, the description gives enough context: what it lists and its current availability. It does not explain optional filters or response format, but no output schema is provided and the tool's main caveat is clearly stated.

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 only 25%; only skill_id has a 'Freelancers only.' description. The description text itself does not explain page, country_id, or the meaning of profile_type beyond the enum values, so parameter semantics remain largely undocumented.

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 title 'List freelancers or employers' clearly states the tool's purpose, and the description 'Directory listing' reinforces it. The description could be slightly more explicit about returning profile directory entries, but it is understandable.

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 explicitly notes that the tool 'currently answers 404 for regular tokens', which sets clear expectations about when not to rely on it. It also explains that it is kept for completeness and potential future access, giving useful context for whether to call it.

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