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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, and openWorldHint=false, covering the safety profile. The description adds that it returns specific data (affiliate RefId, review status, issued links) and requires an access secret. It does not disclose error conditions, rate limits, or secret sensitivity, but adds useful return context beyond annotations.

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, front-loaded sentence with no wasted words. The list of returned fields is efficient, though it is slightly dense and could benefit from clearer structure.

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?

With no output schema and annotations covering the safety profile, the description does supply the return contents and the required key. However, the unexplained 'application_id' and lack of usage context leave meaningful gaps for a tool with 0% schema coverage.

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%. The description only mentions 'access secret' as the key, which restates the parameter name without adding format or source. The required 'application_id' parameter is completely unaddressed, so the description barely compensates for the missing schema documentation.

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 verb 'Fetch' and the specific resource 'instant-link request, affiliate RefId, review status, and issued links' clearly state what the tool does. It also specifies the retrieval key ('access secret'). However, it does not explicitly distinguish this from siblings like request_tracked_links or list_deals, though the scope is narrow.

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 explicit when-to-use guidance or mention of alternatives. The description implies it is used to fetch a request by access secret, but offers no prerequisites, exclusions, or context about when this tool is preferred over similar siblings.

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