ig_publishing_limit

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 does communicate the relevant quota window (50 posts/24h) and clearly implies a read-only status operation, but it does not explicitly say the call is side-effect-free or describe behavior at the limit.

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 a single focused sentence with no filler, front-loading the core quota and limit information. Every word earns its place.

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?

Although an output schema exists, the definition still lacks operational context: when to invoke the tool, what ig_user_id refers to, and any permission or scope requirements. The minimal text is enough to understand the tool's purpose but not to call it confidently in all situations.

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% and the description never mentions ig_user_id. The agent gets no guidance on what identifier to pass, its format, or how to obtain it, so the description does not compensate for the bare schema at all.

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 name and description clearly identify a specific resource: remaining Instagram publishing quota, with the concrete limit of 50 posts per 24 hours. This distinguishes it from sibling publish and insight tools, though it lacks an explicit verb like 'get' or 'check'.

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 notion of 'remaining quota' implies this should be checked before publishing on Instagram, but the description does not explicitly state when to call it, what conditions warrant it, or how it relates to publish operations such as ig_publish_image or ig_publish_reel.

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