List skills

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

Annotations already establish readOnlyHint and openWorldHint. The description adds useful behavioral facts beyond that: skill ids are the only actually enforced feed filter, and names are returned according to FREELANCEHUNT_LANG. This gives the agent meaningful runtime expectations.

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 sentences, each earning its place: scope, usage ordering, and localization behavior. The most important information is front-loaded and there is no fluff.

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 read-only catalogue tool with zero required parameters, the description covers scope, usage context, and an important behavioral nuance. It does not describe the summary vs raw return shapes, but the format enum in the schema partially covers that, and the tool is simple enough that this is a minor gap.

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 67%, covering group and search but not format. The description itself adds no parameter-level detail, so it does not compensate for the format gap. However, the schema already documents most parameters, so the baseline of 3 is appropriate.

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 states a specific resource ('full skill catalogue with ids and groups') and clearly differentiates the tool from siblings by explaining that skill ids are the only feed filter the API enforces and that callers should start here before list_projects or find_projects.

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: 'start here before calling list_projects or find_projects'. It names the relevant siblings and explains why this ordering matters, which is actionable for an agent.

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