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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint=false. The description adds some useful context beyond that, notably no-auth example calls and live marketplace listings labelled by operator, but it does not discuss rate limits, output shape, or other operational details.

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 no filler, listing exactly what the tool returns. It is slightly list-like and does not front-load the primary 'use this to get started' purpose, but it is appropriately sized for the tool's complexity.

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 zero-parameter onboarding tool with rich annotations and an output schema, the description is nearly complete: it explains the content and mentions live data provenance. The main missing piece is explicit guidance that this should be called before the other Voidpay and board tools.

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, so there is no parameter semantics burden beyond the baseline. The schema is empty and fully documented, and the description appropriately does not invent parameter details.

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 makes clear that this is an onboarding/help tool by listing its returned content: connector overview, no-auth example calls, next step, and live marketplace/storefront data. It is specific enough to distinguish it from the board and voidpay action tools, though it does not explicitly state a verb like 'returns' or 'call this first.'

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 does not say when to use this tool, when not to use it, or which sibling tools it should precede. The name and title imply an onboarding entry point, but the description itself provides no explicit usage guidance or alternatives.

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