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

Annotations are empty, so the description carries the full burden of behavioral disclosure. It does reveal ranking criteria such as probability-adjusted expected gross profit and time-to-cash, but it does not state whether the tool is read-only, whether it performs any external action, what it returns, or what side effects it might have.

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 that opens with the verb and resource. The list of ranking criteria is dense but relevant and not padded. Every word earns its place.

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?

This is a complex tool with two parameters, nested objects, no output schema, and no annotations. The description only conveys ranking intent and criteria; it omits output structure, route representation, the meaning of 'signal', and any behavioral/usage context. It is not sufficient for reliable invocation.

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 schema provides zero coverage: 'routes' is an array with an empty item schema and 'signal' is a generic object. The description partially clarifies 'routes' by naming direct service, marketplace work, referral, data/API, product, and other monetization routes, but it says nothing about how these are represented or what 'signal' means. With 0% schema coverage, this is insufficient.

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 a specific verb ('Rank') and a concrete resource ('monetization routes'), and enumerates the route categories and ranking criteria. It is easy to distinguish from sibling tools by task, though it does not explicitly contrast itself with any sibling.

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?

There is no guidance on when to use this tool versus alternatives, no prerequisites, no exclusions, and no workflow context. An agent cannot determine whether this should be called before or after other tools, or what conditions warrant its use.

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