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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=false. The description adds substantive domain behavior by spelling out the exact threshold rules (e.g., > AED 40m with a category > AED 4m triggers the TP Disclosure Form). It does not describe return format or handling of missing optional parameters, but it meaningfully extends the safety profile with evaluation logic.

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?

A single sentence front-loads the core action ('Check which UAE transfer pricing documents apply') and then efficiently enumerates the conditions. Every clause carries necessary threshold information with no filler.

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?

The description gives the governing rules and all five parameters are schema-documented, but there is no output schema and the description does not state what the tool returns (e.g., a list of applicable documents) or how it behaves when optional inputs are omitted. For a check tool with zero required parameters, that gap keeps completeness at a minimum viable level.

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 100%, so the schema already documents each parameter's meaning. The description nevertheless adds value by mapping those parameters to decision thresholds (revenue > AED 200m, relatedPartyTotal > AED 40m, connectedPersonPayments > AED 0.5m, etc.), giving rule-level semantics beyond the raw field definitions.

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 ('Check which UAE transfer pricing documents apply') and resource (UAE TP documents), and even enumerates the thresholds for each document. It is highly specific, but it does not explicitly differentiate itself from any sibling tool (though no sibling appears to be a near-equivalent).

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?

Usage is implied: call this tool when you need to determine which UAE transfer pricing documentation obligations apply. There is no explicit 'use when' clause, no exclusions, and no named alternative among the siblings, so guidance remains at the implied level.

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