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

Annotations already declare readOnlyHint=true and destructiveHint=false, so safety is covered. The description adds valuable context: the 'Main' CryptoCurrency entry is protected and cannot be overwritten, with changes silently ignored. However, this is about write behavior for a read-only tool, which is slightly tangential, and no return format or pagination is described. The protected-key note is useful but doesn't fully compensate for a read tool's behavioral gaps.

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 information-dense but front-loaded with the key scoping statement. However, it includes a lengthy explanation of the Currency catalogue and its references that, while informative, is somewhat verbose for a simple getter. Every sentence earns some place, but the note about protected 'Main' entry is more relevant to save_currency.

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 the tool's complexity (1 param, no output schema, rich annotations), the description provides substantial context about what Currency contains and how it relates to other systems. It is nearly complete, though it could clarify that this returns a configuration object without a schema.

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 the schema fully documents the single title_id parameter. The description doesn't add parameter-specific syntax or format details. With 0 params needing explanation beyond the schema, baseline 4 applies per the rule for 0 params.

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+resource: GET only the 'Currency' field of TitlePublicConfigurationModel. This is highly specific and distinguishes it from siblings like get_item or get_store, which are separate configuration domains.

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 explaining what the Currency catalogue is and that CurrencyID is referenced by Item prices, Store SKUs, and other systems, giving context for why an agent would call it. However, it doesn't explicitly state when to use this versus alternatives like save_currency or get_item, leaving usage inferred rather than stated.

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