instagram_login_status

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

The description goes well beyond the annotations: it states the tool never logs in and never contacts Instagram (stronger than readOnlyHint), and clarifies that the configuration object reports which credentials are set but never their values. This adds critical behavioral context that annotations alone do not provide.

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 efficiently structured with a clear opening sentence, a usage guidance paragraph, and a return-value list. Every sentence adds value—there is no filler or redundancy. It front-loads the key message about safety and non-contact.

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 diagnostic tool with an output schema, the description is fully complete. It explains the purpose, when to use it, and exactly what is returned. The presence of an output schema means the description does not need to repeat schema details, yet it still summarizes the return fields clearly.

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 no parameters, so the baseline is 4 per rubric. The description does not need to explain parameters, and it does not mention any. It appropriately focuses on behavior and return values.

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 states the tool reports session status and server configuration, and explicitly distinguishes itself from instagram_login by declaring it never logs in and never contacts Instagram. This makes its purpose precise and clearly separates it from the large set of sibling tools.

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?

It provides strong context: 'safe first call when something is not working' and lists concrete intended uses (check which account, write permissions, credentials present). It does not explicitly name alternatives, but the 'never logs in' statement implies it is not for login actions. The guidance is clear enough without being exhaustive.

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