ironscales_navigate

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

No annotations provided, so the description must do more. It implies a non-destructive read operation ('see its available tools'), but does not confirm no side effects or specify behavior beyond navigation. Slightly vague.

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 sentences with a clear list. Every sentence is necessary and no redundancy. Extremely concise and well-structured.

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 simple navigation tool with one parameter and no output schema, the description is fully complete. It lists all domains with brief explanations, and no additional context is needed for correct usage.

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?

The description adds significant meaning to the 'domain' parameter by explaining each enum value (e.g., 'incidents (phishing incidents)'), which goes beyond the schema's simple description. Schema coverage is 100% but description enhances clarity.

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 'Navigate to a domain to see its available tools,' uses a specific verb and resource, and lists all valid domains. It distinguishes itself from the sibling tool 'ironscales_status' which likely checks status.

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 explicit guidance on when to use (to see tools for a specific domain) and enumerates valid domains. However, it does not explicitly mention when not to use or alternative tools, though the context is clear.

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