Create address object (safe)

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

Discloses the default dry_run=true and the apply workflow, which is critical for safety. Annotations indicate non-idempotent, non-destructive, write operation; description aligns. Missing info on idempotency, but overall good transparency.

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: one for purpose, one for usage. No redundant words, front-loaded with key information.

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?

Adequate for a create tool with complete schema. The safety workflow is explained. No output schema mentioned, but not needed. Minor gap: no mention of error behavior or whether duplicate names cause idempotent updates or errors.

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 covers all 7 parameters with detailed descriptions (100% coverage). Description only reiterates the dry_run default and confirm requirement, adding no new semantic value beyond 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?

Clearly states the verb 'create' and resource 'firewall address object'. The 'safely' qualifier and mention of dry_run=true distinguish it from sibling tools that might be more direct or destructive.

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?

Provides guidance on using dry_run and confirmation for safety, but does not explicitly advise when to choose this tool over alternatives like fortigate_create_address_group or fortigate_update_address. No when-not-to-use or exclusions.

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