rynmesh_credit_scoreboard

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It does indicate a read-like operation returning ranked accounts, but it does not explain what 'visible' means, how distribution weight is computed, which ranking direction is used, or whether any side effects or permissions are involved.

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 front-loaded sentence with no filler: it leads with the action and the resource. It loses one point because the extreme brevity omits the parameter and usage context that would make the description genuinely helpful, but as written it is efficient.

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?

The tool is simple, with one optional parameter and no output schema, so the description should clearly cover that minimal surface. It does not explain the category parameter, the meaning of 'visible', or the expected ranking behavior, leaving the agent with an under-specified call contract.

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 0%, and the description never mentions the 'category' parameter. The agent cannot determine whether category is a filter, a dimension, or something else, nor what values are acceptable. Since the description must compensate for the low schema coverage and does not, parameter semantics are effectively absent.

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 verb ('Return'), a distinct resource ('Rynmesh Credit accounts'), and a ranking criterion ('by distribution weight'), so the core purpose is clear. However, it does not distinguish this tool from the related sibling rynmesh_credit_summary, so it stops short of full sibling differentiation.

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 no guidance on when to use this tool versus alternatives such as rynmesh_credit_summary or rynmesh_record_credit_event. There are no explicit conditions, exclusions, or preferred-use scenarios, so the agent is left to infer usage from the resource name alone.

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