get_publishing_limit

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

No annotations are provided, so the description bears the full burden. It discloses the key behavioral detail: the exact quota window and counting rule, which is useful. However, it does not state whether the operation is read-only, what the return value looks like, or any side effects. The description is partially transparent but lacks return-format and safety context.

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, compact sentence that packs the necessary quota information and usage trigger into minimal words. Every phrase is informative: the quota value, the rolling window, the carousel counting rule, and the use case.

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 zero-parameter read-only discovery tool, the description provides the essential facts: quota limit, time window, and when to invoke. The lack of return-value specification is a minor gap since the operational context is otherwise clear. The description is complete enough for an agent to successfully use the 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?

This tool has zero parameters, so the baseline is 4. The description correctly focuses on the quota details rather than parameter explanations, which are unnecessary. The description adds value by explaining the quota semantics that would otherwise be opaque.

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's purpose: retrieving Instagram's publishing quota with specific details (100 posts per 24-hour rolling window, carousel counts as 1). It uses the verb '查' (check) and names the exact resource, making it distinct from siblings which handle publishing and token management.

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 says to check this when publishing failures are suspected to be caused by rate limiting, providing a clear when-to-use. It does not mention when not to use it or alternatives, but for a simple quota lookup this guidance is sufficient and actionable.

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