instagram_guide

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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so the safety profile is covered. The description adds that the content is instructional rather than live account data, but says nothing about the form of the instructions or how the default 'overview' topic behaves.

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?

A single front-loaded sentence with no filler. It is tight, though 'practical instructions' is slightly vague for a definition that must carry all topic semantics.

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?

An output schema exists, so return values need not be explained. The main residual gap is the set of valid topic strings, which the agent must guess, but for a simple one-parameter guide tool this is close to adequate.

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 coverage is 0% and the single `topic` parameter has no enum, so the description is the only signal — and it only loosely gestures at valid areas (authentication, Reels, account reads, UI actions) without stating that these are the accepted topic values or mentioning the 'overview' default.

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?

States a specific verb and resource: reading practical instructions, and names the covered areas (authentication, Reels, account reads, UI actions). That implicitly separates it from the action siblings like instagram_login_start or instagram_reel_start, though it never says so explicitly.

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?

Usage is only implied — an agent can infer this is a documentation lookup to consult before or alongside the action tools, but the description never says 'use this before calling X' or when this is unnecessary.

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