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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered structurally. The description adds nothing beyond the path and a pointer to describe_operation — no note on what the configuration contains, whether it is workspace-scoped, or any output shape.

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 one substantive sentence is duplicated verbatim, which is pure waste, and the remaining content (operation ID) is a machine artifact rather than useful guidance. Being short does not make it concise when half the text is redundant.

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?

With no output schema and a fully undocumented free-form query parameter, the description must carry the load, yet it never says what the currency configuration returns or what the endpoint's inputs mean. It is not sufficient for an agent to invoke the tool correctly.

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?

Two parameters exist (a free-form 'query' object with arbitrary keys and an empty 'params' object) and schema description coverage is 0%. The description says nothing about either parameter, so an agent has no idea what may be passed to 'query' — the exact case where the description needed to compensate.

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 is nothing but the raw endpoint path repeated twice, which merely restates the tool name/title (global-settings currency-config). It does identify a resource via the URL, but offers no explanation of what the returned currency configuration actually is or how it differs from sibling tools like get_global_settings_supported_currencie or get_global_settings_fiscal_config.

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 statement of when to use this tool versus the many global-settings siblings. The only routing hint is 'describe_operation provides native request schemas', which points to another tool for schema lookup, not to a usage condition.

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