aircraft.profile

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

No annotations provided; description returns aircraft record and sanctions screen with confidence and flagged, and notes name-based screening is probabilistic, but lacks details on permissions or what happens if aircraft not found.

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 concise sentences that front-load the key action and deliver essential information without waste.

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?

Given no output schema or annotations, the description adequately explains return values (aircraft record + sanctions screen) and the probabilistic nature, though it misses some conditional behaviors.

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?

Description adds context for tail and icao24 as identifiers, but threshold parameter is not explained despite being mentioned indirectly as probabilistic. Schema coverage is 67%.

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 clearly states the tool identifies US-registered aircraft by tail or ICAO24 and screens owner/operator against OFAC sanctions, distinguishing it from sibling tools like aircraft.lookup.

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 implies use for OSINT/asset-tracing/sanctions-evasion but does not explicitly state when not to use it or list alternatives like aircraft.lookup for simple lookups.

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