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

Annotations already declare readOnlyHint, idempotentHint, non-destructive, and closed-world, so the safety profile is fully covered elsewhere. The description adds only the endpoint path and a pointer to describe_operation; it discloses nothing about filtering behavior, response shape, or auth scope beyond the annotations.

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 identical endpoint sentence appears twice, so half the text is pure duplication, and none of it is front-loaded with meaning. The operation ID is filler for an agent.

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, no parameter documentation, and an empty params object, the description leaves the agent unable to determine expected inputs or return shape. Only the redirect to describe_operation keeps it from being entirely unusable.

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 0% for two parameters (a free-form 'query' object and an empty 'params' object), and the description says nothing about what goes in either. The pointer to describe_operation is the sole compensation, which is thin for a 0%-coverage nested 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?

The description is a bare restatement of the HTTP method and path already present in the name and title ('GET /api/global-settings/ai-import-config'), repeated twice. It does not say in prose what the AI import configuration contains or how it differs from siblings such as get_global_settings_currency_config 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 when-to-use or when-not-to-use guidance and no named alternative among the many get_global_settings_* siblings. The only directional hint is 'describe_operation provides native request schemas', which tells the agent where to get schemas, not when to invoke this tool.

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