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

Annotations already declare readOnlyHint and openWorldHint=false, so the safety profile is covered. The description adds genuinely useful behavior: results are limited to already-published videos, scoped to the agency's own Instagram, and it enumerates the returned fields (ref, title, type, post date, length, IG link) despite there being no output schema.

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, no filler, and the audience constraint is front-loaded before the search behavior and return fields.

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 read-only, no-output-schema search tool it is nearly complete: eligibility, search semantics, downstream ref usage, and return fields are all stated. The only gap is pagination/limit behavior for the limit and offset parameters.

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 description coverage is 0%, so the description must carry the load. It explains the query parameter well (title/caption keyword search with concrete examples), but is silent on limit (max 30) and offset, leaving two of three parameters undocumented anywhere.

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?

It names the exact resource (Shorts and Reels ShearQuery has already published) and the scope/audience (an APPROVED AGENCY reposting to its own Instagram). An agent can distinguish this from siblings like my_instagram_posts or queue_agency_post without opening any 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?

It states the eligibility precondition (approved agency) and how to search (words in title or caption, with examples). It also routes the agent forward by naming queue_agency_post as the consumer of the returned ref, though it does not state explicit when-not conditions or a sibling alternative for browsing non-published content.

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