Instagram Connection Status

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

The description adds context by stating it 'reports the current login or session state' and 'never asks for credentials,' providing safety-relevant behavior beyond the annotations. Annotations already hint at idempotency and non-destructiveness, and the description does not contradict them.

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 two sentences, front-loaded with the primary use case. Every sentence adds value: one tells when to use it, the other clarifies what it reports and that it doesn't ask for credentials. No redundancy.

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?

Given the tool's simplicity (no params) and the presence of an output schema, the description adequately covers the core behavior and usage context. It mentions the important LOGIN_PENDING scenario and the credential-avoidance behavior, providing sufficient completeness for an AI agent.

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, and the input schema confirms this with 100% coverage. The description does not need to add parameter semantics, and per the rubric, a tool with 0 params receives a baseline of 4, which is appropriate here.

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 the tool checks whether Instagram is connected and reports the current login/session state. This specific verb+resource combination distinguishes it from sibling tools like instagram_connect and instagram_disconnect.

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?

The description explicitly says to use this when checking connection status, especially after instagram_connect returned LOGIN_PENDING. It provides clear context but does not explicitly state when not to use it or mention alternatives beyond the implied distinction from connect/disconnect.

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