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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), and the description adds real behavior: default A-Z ordering, that ZeroCrew does not rank results, that the response echoes which sort order was used, and a hard cap of 50 results. The 50-result cap is stated without saying how to page past it, which is the main remaining gap.

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?

Front-loaded with the purpose, then ordering, then the limit, then the sibling pointer — a sensible order with little waste. The 'ZeroCrew doesn't rank them' sentence is slightly redundant with the sort explanation that follows.

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?

There is no output schema, so the description carries the return-value burden, and it does state result count limits and that the chosen order is echoed. It is nearly complete for a simple filtered list, falling short only on what happens when more than 50 tools exist.

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 coverage is 100%, so the baseline is 3, but the description earns more: it explains what must_use and using_now actually mean (counts of developers rating a tool a must-use or using it now) rather than just restating the enum, and it supplies example role/job values.

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 first clause names a specific verb and resource (list the tools for one job) and scopes it to the ZeroCrew directory with a concrete example. It also distinguishes itself from list_roles, which is named as the tool for browsing every role and job.

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?

It gives a clear usage context (need the tools for one role+job) and routes role/job discovery to list_roles. It explains when to pick each sort mode. It doesn't explicitly exclude search_tools or get_tool, so the sibling boundary is only partially drawn.

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