ie_get_started

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

The description adds "No network," which is valuable behavioral context beyond the annotations: the tool performs no network calls and is safe/fast to invoke. Combined with the annotations indicating read-only, idempotent behavior, the agent has a clear safety profile.

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?

The description is a single compact sentence that front-loads the most important directive ('Start here') and then lists the contained content in a scannable series. Every word contributes meaning.

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 zero-parameter, read-only, idempotent guide tool with an output schema, the description covers what the tool is for, what it contains, and its network behavior. Nothing critical is missing.

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 tool has zero parameters, so there is no parameter semantics burden on the description. A baseline of 4 is appropriate because nothing about parameters needs explaining.

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 identifies this as a starting point containing setup instructions, browser sign-in steps, usage examples, and scope. It distinguishes itself from the many data-access sibling tools by framing itself as an onboarding/guide tool rather than a data operation.

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?

"Start here" explicitly tells an agent when to invoke this tool: before engaging with other tools. It provides clear context for first use, though it does not explicitly name alternatives or state when not to use it.

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