defensetech_check_itar_us_person

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

No annotations provided, so description must carry full burden. Description lacks details on side effects (read-only vs write), authorization needs, return format, error behavior, or rate limits.

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?

Single sentence with regulatory reference, no wasted words. Front-loaded with core condition. Efficient but could benefit from slight structure to highlight parameter mapping.

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 compliance check tool with 3 parameters and no output schema, description lacks return value specification (boolean? success/error?), does not clarify optional vs required params, and omits error conditions. Significant gaps given tool's purpose.

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 has 0% description coverage. Description mentions condition involving US-PERSON-VERIFIED and AUTHORIZED-FOREIGN-PERSON-WITH-LICENSE, which maps to likely parameter roles, but does not explicitly define each parameter's meaning or valid values.

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?

Description clearly states the tool checks ITAR resource event for US-PERSON-VERIFIED or AUTHORIZED-FOREIGN-PERSON-WITH-LICENSE + DDTC license number. Cites specific regulations. Unique verb-resource combination distinguishes it from siblings.

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?

Implied usage for verifying ITAR compliance, but no explicit when-to-use vs alternatives or exclusions. Does not mention sibling tools or when not to use.

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