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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds only the workspace scoping; it says nothing about ordering, result size, or what an empty result means for a tool whose whole job is enumerating accounts. Useful but thin beyond the structured fields.

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 the purpose front-loaded, but the usage sentence restates the same idea three times ('what accounts are tracked', 'see their monitored accounts', 'which accounts are in their workspace'). It is padded rather than dense.

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 no-parameter read-only list with no output schema, the description tells the agent enough to call it and interpret the result as 'the monitored Instagram accounts.' Minor gaps (ordering, whether empty means nothing is connected) do not block correct invocation.

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?

Zero parameters, so there is nothing for the description to disambiguate; the baseline applies. No parameter text is needed and none is missing.

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 (List) and resource (Instagram accounts currently being monitored) plus the scope ('in your OwlStat workspace'). The Instagram qualifier cleanly separates it from the sibling list_tiktok_monitored_accounts, so an agent can pick the right one without opening a schema.

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?

Gives clear triggering conditions: 'when someone asks what accounts are tracked, wants to see their monitored accounts, or needs to know which accounts are in their workspace.' It stops short of naming alternatives or exclusions—it never points at list_tiktok_monitored_accounts or the stats tools for follow-up—so the routing is implied rather than explicit.

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