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

No annotations are provided, so the description carries the full burden. It clearly marks this as scheduler-side/read-only, notes that it returns only a summary payload, explains superlative handling via sortOrder and limit, and describes pagination with nextCursor/cursor. It also discloses the prerequisite behavior: call it directly without listing accounts first.

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 dense but every sentence earns its place. It front-loads the core purpose, then adds exclusions, alternatives, return shape, and operational patterns without redundancy. Emphasis and line breaks make the long content scannable.

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 list tool with no output schema and no annotations, the description is unusually complete: it names the returned fields, explains pagination, gives superlative patterns, and routes all relevant sibling cases. The only minor omission is the platform parameter, but the parameter name plus the rest of the guidance make the tool safe to invoke.

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?

With 0% schema description coverage, the description must compensate. It does well for sortOrder ('asc' oldest, 'desc' newest), limit (with sortOrder for superlatives), and cursor (pass previous nextCursor). However, it never explains the platform filter parameter and only loosely maps status values to the schema enum, so it is not a perfect 5.

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 and resource: 'List posts from the SociaHive Content Scheduler' and scopes it to drafts, queued, recurring, and published-via-scheduler entries. It also distinguishes from platform-published content and names the returned fields, so there is no ambiguity about what this tool does.

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?

Explicitly lists when to use it ('what's scheduled this week', 'show my drafts', failed publications, queue-side history) and when not to use it. It names direct alternatives: write/bulk tools for changes, list_published_media for platform-side posts, and get_post for full content, and even says not to call list_accounts/whoami first.

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