Carry Console — MCP App

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is covered. The description adds real behavioral context beyond that: the 402 challenge is the authoritative price/entitlement source and no data is returned before authorization, which tells the agent to expect an entitlement gate and an empty pre-auth response.

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 tight sentences with the action front-loaded and no filler. The entitlement caveat earns its place, though the phrase 'price and entitlement source of truth' is slightly dense.

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?

An output schema exists, so return-value description is not required, and annotations cover the safety profile. The authorization prerequisite is disclosed, but the lone input parameter is left unexplained in both schema and description — a minor gap in an otherwise complete definition.

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%, so the description must compensate for the single 'interaction' parameter, and it does not mention the parameter or the 'ui_refresh' enum value at all. The enum is fairly self-explanatory, but the description adds zero meaning for the one input an agent must supply.

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 pair (fetch and render) and a specific resource (the existing paid /carry/opportunities result). An agent can tell this is a display/scan tool rather than a data-producing search. Slightly undercut by the ambiguous 'render one read-only opportunity', which doesn't clarify whether exactly one item is returned or a list previewed.

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?

The description implies a prerequisite context — the upstream HTTP 402 challenge gates access — which hints at when the tool can usefully be invoked. However, it gives no explicit when-to-use/when-not guidance and no alternative tools (there are no siblings), leaving the payment-flow trigger to inference.

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