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

Annotations already establish readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds meaningful context beyond that: the approval precondition, the concrete slot times (9 AM / 2 PM / 7 PM ET), and the fact that content is Reels of ShearQuery's videos on the agency's own Instagram rather than arbitrary uploads. It stops short of describing ordering guarantees or limits on the returned queue.

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, zero filler, with the gating condition ('For an APPROVED AGENCY') front-loaded before the enumerated payload. Every clause earns its place by naming a distinct piece of returned data.

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?

With no output schema, the description carries the burden of conveying the return shape and does so well by enumerating connection, schedule with slot times, ordered post line, and posted/failed status. It is complete enough to call correctly; only the queue's size or pagination behavior is left unstated.

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 takes zero parameters and the schema is empty, so there are no parameter semantics to document and the baseline of 4 applies. Nothing in the description misleads about inputs.

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 names a specific resource (the agency's Instagram connection, schedule, post queue, and results) and scopes it to an APPROVED AGENCY, which separates it from personal-account siblings like my_instagram_posts and my_posts. It is a status/read view rather than a clear verb-led action, so it is clear but not maximally sharp.

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 phrase 'For an APPROVED AGENCY' supplies a real precondition (the agency must be approved), which is genuine usage context. However, it never states when to call this versus the obvious alternatives that mutate the same domain (queue_agency_post, update_agency_post, set_agency_publishing_schedule), leaving the read-vs-write routing to inference.

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