Money-making methods

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

Annotations already cover readOnly/idempotent/openWorld/destructive, so the description's job is lighter. It adds real behavioral context beyond them: results are filtered by category/members/recurring/min gp/hr and 'checked against the account', implying personalization to the saved or named player, plus cursor-based continuation of long lists.

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 triggering condition and then the capability; two sentences with no filler. Slightly dense with filter enumeration, but each element 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?

For a 7-param, all-optional list tool with no output schema, the description covers the trigger, the filtering surface, pagination, and account-checking behavior. It does not describe the response fields, though the account-check behavior arguably needs one clarifying clause.

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 100%, so both filter params and pagination (limit, cursor) are already documented in the schema; baseline 3 applies. The description adds only the output ordering signal ('by gp/hr'), not syntax or format detail beyond the schema.

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?

States a specific verb and resource: 'Lists the wiki's money-making guides by gp/hr'. The scope (guides, ranked by gp/hr, filterable) is precise enough to distinguish it from siblings like get_price or plan_skill.

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?

Explicit trigger: 'Use when the player asks how to make money.' That is a clear when-to-use condition, but no when-not or named alternative tool is given for adjacent needs (e.g. single-item profitability via get_price).

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