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

With no annotations, the description carries the full burden, and it does disclose the one non-obvious behavior: check=true triggers an on-chain payment lookup. It says nothing about authentication (the bearerToken parameter exists but is unexplained), latency or failure behavior of the on-chain check, or what statuses can come back.

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 short sentences, front-loaded with the primary action and scope, with the conditional usage note second. Nothing is redundant or padded.

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 three-parameter read tool with no annotations and no output schema, the description should explain the bearerToken/auth expectation and at least hint at the returned shape beyond 'status'. It covers the core retrieval and the check flag adequately, but leaves the auth parameter and response contents ambiguous.

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 coverage is 33%: id has only a trivial description and both check and bearerToken are undocumented. The description compensates for check by explaining that true means an on-chain lookup, but bearerToken remains entirely unexplained in both schema and description.

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 and resource ('Get one GotSOL.app payment link') plus the payload content ('including status'), which clearly separates it from list_payment_links. It does not explicitly name the sibling it differs from, but 'one' implies single-record retrieval.

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?

There is no statement of when to use this versus list_payment_links or get_payment_history; retrieval-by-id is only implied. The one conditional sentence ('Set check to true...') is parameter guidance, not tool-selection guidance, and no exclusions or prerequisites are given.

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