Get efficiency rates config

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 only states that the tool fetches configuration, with no mention of side effects, authentication requirements, rate limits, or other behavioral traits. For a read-only tool, this is minimal disclosure.

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 sentence that is front-loaded with the main verb and resource. It is concise, contains no redundant information, and every word adds value.

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 there is no output schema, the description provides a reasonable hint about the return structure ('xp/hr or kills/hr rates per skill or boss'). It covers the input parameters and the tool's purpose. However, it could be more explicit about the output format.

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 coverage is 50%: the 'metric' parameter lacks a description. The description adds some context ('xp/hr or kills/hr rates per skill or boss') but does not directly describe each parameter. It helps infer that 'metric' determines EHP vs EHB, but does not fully compensate for the missing schema description.

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 action ('Fetches') and the resource ('current EHP/EHB rate configuration used for a given account type'). It effectively distinguishes this tool from siblings like wom_get_efficiency_leaderboard, which returns leaderboard data rather than configuration.

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 usage by stating what the tool does, but it lacks explicit guidance on when to use this tool versus alternatives (e.g., wom_get_efficiency_leaderboard). No when-not-to-use or prerequisites are provided.

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