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

Annotations already provide readOnlyHint, idempotentHint, and destructiveHint, covering the core safety profile. The description supplements this by clarifying it is only a catalog, listing the informational content, and saying no authentication is needed.

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?

Three short, focused sentences with no filler. The most important distinction 'Catalog only' is front-loaded, followed by the content summary and the follow-up action.

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-input, no-output-schema, read-only catalog, this is complete: an agent knows why to call it, what it will contain, and the next step. Nothing needed for invocation or correct behavior is missing.

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 schema has zero parameters and existing properties, so full coverage is given and the description correctly implies no input is required. The additional 'No authentication required' and 'Call apply next with...' context helps distinguish this from next steps, though no parameter semantics are needed beyond the empty schema.

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 specific verb and resource: it is a catalog and a read-only informational tool, not an application. It distinguishes itself from sibling tools by naming the 'apply' flow and listing the catalog content (integration model, payout terms, tool list).

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 explicitly frames this tool as a non-application prerequisite and instructs the agent to call 'apply' next with the exact parameters. It also states that no authentication is required, which helps the agent decide when to invoke this safely.

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