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 genuinely useful behavior: the view spans today plus a backlog of unposted earlier comments and reports 7-day fullness against a 5-per-day cap, which hints at a queue quota. It stops short of stating pagination, ordering, or what 'draft' means operationally.

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?

It is a single sentence, but it opens with an audience preamble ('For the ShearQuery team') rather than the function, and then chains three loosely joined clauses with dashes. The information is there but not front-loaded or cleanly structured.

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 does the work of telling the agent what comes back: per-comment post links and drafts, a backlog section, and a forward-looking capacity count. That is sufficient for a single-optional-param read tool, though ordering and pagination remain 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?

Only one parameter with 100% schema description coverage ('YYYY-MM-DD (Eastern). Default today.'). The description repeats the default-today behavior but adds no format, timezone, or boundary semantics beyond the schema, so the baseline 3 applies.

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?

Names the resource ('the comment calendar') and enumerates what it contains: one day's comments with post link and draft, earlier unposted comments, and next-7-day capacity. The verb is implicit (view/list) rather than stated, and the 'For the ShearQuery team' framing is audience-scoped rather than functional, but an agent can still tell this apart from update_ig_comment or queue_ig_comment.

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 'default today' note implies a routine check-in use, but there is no explicit when-to-use, no condition for passing a date, and no routing against siblings like ig_engagement_targets, my_instagram_posts, or shearquery_instagram_activity. The agent must infer context.

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