xpayr_get_merchant_profile

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

No annotations are supplied, so the description carries the full disclosure burden. 'Retrieve' implies read-only, but it says nothing about authentication requirements, whether API keys are returned masked or in plaintext (a meaningful security consideration), rate limits, or error behavior for unauthenticated calls. Beyond listing return fields, there is little behavioral context.

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?

One sentence, front-loaded with the verb and resource, with zero filler. The parenthetical '50 bps = 0.5%' earns its place by removing an interpretive ambiguity in a returned field.

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 no parameters, the description must define return content, and it does so thoroughly. The remaining gap is behavioral rather than structural: it does not say what happens without valid credentials or whether sensitive fields are redacted.

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, which is the baseline-4 case. The description correctly adds nothing about inputs and instead spends its words on output fields, which is the right allocation.

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?

Specific verb ('Retrieve') plus a precise resource ('authenticated merchant profile') and an explicit enumeration of the returned fields (business name, settlement wallet, commission rate, API keys, livemode). An agent knows exactly what it gets. It does not explicitly contrast itself with siblings like xpayr_get_merchant_balance, though the 'profile' framing makes the distinction reasonably obvious.

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 only implied: the word 'authenticated' signals that the caller must hold credentials and that this returns the calling merchant's own data rather than an arbitrary merchant's. There is no explicit when-to-use or when-not, and no mention of an alternative tool for balance, sessions, or public status.

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