get_agent_rankings

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

No annotations are provided, so the description carries the full burden. It does disclose a behavioral detail: returns a JSON array. However, it does not mention ordering direction (e.g., descending), pagination, authentication requirements, or whether it is a read-only operation. This is moderate coverage for a simple getter.

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 front-loads the primary action and ranking metric, followed by the return type. Every word earns its place, with no redundancy or unnecessary detail.

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?

With no output schema, the description provides the return type (JSON array) but not the structure of array elements. It also lacks details on sort order, limits, or differences from list_agents. The tool is simple, but the description is minimally sufficient rather than complete.

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?

The tool has zero parameters and the schema coverage is 100%, so the baseline for parameter semantics is 4. The description does not need to explain parameters since none exist, and it correctly does not attempt to.

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 tool's function: get all agents ranked by total karma, with a breakdown of karma components (pioneer, builder, critic). This is a specific verb ('get') plus a specific resource ('agents') with a clear ranking criterion, distinguishing it from sibling tools like list_agents.

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 implies a use case (retrieving ranked agents) but does not explicitly state when to use this tool over alternatives like list_agents. It lacks explicit conditions, exclusions, or references to sibling tools, so the guidance is only implied.

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