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

Annotations already flag readOnly/idempotent/non-destructive, and the description usefully adds that the call itself is free, that no payment executes inside MCP, and that user approval of the amount is required before paying. This is real context beyond the structured hints, though it omits what happens if the endpoint is unavailable.

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?

Front-loaded with 'Free to call', then the payload, then the payment caveat. Three tight clauses with no filler, though the MPP/Stripe jargon could be ordered more clearly.

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, and the description names the three returned items (endpoint, EUR price, payment-token command), which is adequate for a single-param tool. The main gap is the unresolved ambiguity with get_resident and slug validity.

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?

One required parameter ('slug') with 0% schema description coverage, so the description must compensate. It implies the slug identifies 'a resident' but never defines its format or what a valid slug looks like, leaving partial compensation only.

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 states a concrete outcome: retrieve a resident's paid HTTP 402 endpoint, current EUR price, and the exact payment-token command. The verb 'hire' is vague but the body clarifies it. It does not differentiate itself from the sibling get_resident, which could confuse selection.

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?

It gives useful workflow context ('Free to call', payment happens over HTTP not inside MCP, get user approval of the amount before paying), which implies when it fits. However it never contrasts with get_resident or states prerequisites (e.g., the resident must already be identified/willing).

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