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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint, covering the safety profile. The description adds 'Side-effect-free' and 'read-only widget', which are largely redundant with the annotations. It provides some extra behavior detail by stating it is a dashboard widget, but this is minor and does not substantially extend beyond the structured metadata.

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 description is a single, compact sentence with a parenthetical clarification. Every component adds value: the action, the resource, the content, and the safety note. There is no redundancy, fluff, or unnecessary elaboration.

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?

For a parameterless read-only widget, the description fully conveys the purpose and expected content. It does not need to explain return values since there is no output schema, and the mention of 'PaymentIntents awaiting payment' gives the agent sufficient context. No critical information is missing for a tool of this simplicity.

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 has zero parameters and an empty input schema, so schema coverage is effectively 100%. With no parameters to document, the description correctly omits parameter details, meeting the baseline for zero-parameter tools.

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 uses a specific verb 'Opens', targets a concrete resource ('pending cobros dashboard'), and clarifies the content ('listing PaymentIntents awaiting payment'). It distinguishes itself from siblings like open_cobro_status or open_business_overview by specifying 'pending cobros', making the purpose clear and unambiguous.

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 provides no explicit guidance on when to use this tool versus alternatives such as open_business_overview or get_payment_intent_status. It does not mention conditions, exclusions, or recommend alternative tools. While the name implies a use case (viewing pending orders), there is no direct comparison or contextual instruction.

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