The posting quota that will actually be enforced: tier, posts used, limit and remaining. Check this before composing a batch instead of discovering the limit via errors.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries the full burden of behavioral disclosure. It conveys that the returned quota is the enforced one and implies a read-only, non-error-prone operation by recommending it as a pre-composition check. However, it doesn't mention permissions or side effects, though these are unlikely for a quota getter.
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 two concise sentences. The first sentence states exactly what is returned, and the second provides actionable usage guidance. No wasted words.
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?
Given the lack of parameters and annotations, and the simplicity of the tool, the description is fully adequate. It explains the output fields, the enforcement aspect, and the recommended timing. It complements the sibling list by making it clear this is the quota-checking tool.
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 has zero parameters, so the schema covers everything. The description adds context about what the quota includes, which helps the agent understand the output even though no parameters need explaining.
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 clearly states the tool returns the enforced posting quota, including specific fields (tier, used, limit, remaining). It distinguishes itself from sibling tools by focusing on quota rather than post management, and the reference to batch composition clarifies its unique role.
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 description explicitly advises checking this tool before composing a batch, and warns against discovering the limit via errors. This provides a clear 'when to use' and 'when not to use' (don't wait for errors), which effectively guides the agent in choosing this tool.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Each tool targets a unique resource and action: drafts, scheduled posts, published posts, accounts, analytics, quota, and queue info are all clearly separated. No two tools overlap in purpose; even similar-sounding ones like list_scheduled_posts and list_published_posts are distinct.
All tool names follow a consistent verb_noun pattern with snake_case (e.g., create_post, list_drafts, get_posting_quota). The use of 'list_' for collections and 'get_' for single items/summaries is predictable and logical.
14 tools is well within the ideal 3-15 range and appropriately covers the domain of social media post management, scheduling, drafts, analytics, and account inspection. Each tool serves a distinct function without redundancy.
The surface covers the full lifecycle of posts and drafts: create, read, update, delete, schedule, cancel, and reschedule. Minor gaps exist, such as no direct way to convert a draft into a post, but this can be worked around by copying content.