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

readOnlyHint=true already tells the agent this is a safe, non-mutating read. The description adds that the configuration is the caller's (no identifier needed, auth context implied) and sketches the payload. It stops short of describing permissions required or the response 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?

Two short sentences, purpose first, with the 'caller's' scoping qualifier front-loaded and zero filler. The trailing HTTP route is a minor but cheap anchor.

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?

There is no output schema, so the description carries some return-value burden; it partially discharges that by naming settings and enabled payment methods, but 'etc.' leaves the payload only roughly characterized. For a simple self-scoped getter with readOnly annotations, this is nearly sufficient.

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?

The tool takes zero parameters, so the baseline is 4. There is nothing for the description to disambiguate, and the schema is empty as expected.

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 (Get) plus resource (the caller's Mercoa organization configuration) and even names example contents (settings, payment methods enabled). It is naturally distinguishable from resource-specific siblings like mercoa_get_entity or mercoa_get_invoice, though it never explicitly contrasts itself with them.

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?

Usage is implied by the phrasing — an agent reads this when it needs the current organization's configuration — but there is no explicit when-to-use, when-not-to-use, or named alternative. For a zero-parameter self-scoped read this is acceptable, but nothing is spelled out.

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