rynmesh_rank_clips

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

With no annotations, the description carries the full burden of disclosing behavior. It only says clips are ranked by credit weight; it does not state whether the tool is read-only, changes state, has side effects, or what 'visible clips' means. This is too thin for a tool with no structured safety hints.

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 short, but part of it ('Compatibility tool') is cryptic and earns no value, and the rest is under-specified. This is under-specification rather than effective conciseness.

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?

Given no annotations, no output schema, and two unexplained but optional parameters, the description is not complete enough for an agent to know the result shape, parameter effects, or side-effect profile. The agent could call it with no arguments, but it cannot correctly reason about the available options.

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 does not clarify the 'category' or 'include_invalid' parameters. The mention of 'visible clips' loosely relates to filtering, but it never explains how either parameter changes the ranking or which values are valid.

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 action and resource: 'rank visible clips' by 'Rynmesh Credit distribution weight.' However, the prefixed label 'Compatibility tool:' is ambiguous and does not explain what it is compatible with, so it slightly blurs the core purpose.

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?

No guidance is provided on when to use this tool versus alternatives such as rynmesh_rank_content or rynmesh_list_clips. The phrase 'Compatibility tool' hints at a legacy use case, but no explicit context, exclusions, or preferred alternative is given.

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