Check Threads Publishing Limits

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

Annotations already carry the safety profile (readOnlyHint=true, destructiveHint=false), and the description adds useful context by disclosing the quota (250 posts per 24 hours) and the return shape (current usage and limit). No contradiction with annotations. It does not go deeper, but the annotation coverage lowers the bar.

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 compact: a single purpose sentence followed by Args and Returns. The purpose is front-loaded and there is no filler, though the Args block is somewhat redundant with the input schema.

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 low-complexity, read-only tool with no output schema, the description covers the essential contract (usage vs. quota). It is adequate but lacks guidance on when to check limits during a publishing workflow and does not mention how the response_format parameter affects output.

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 schema coverage at 50%, the description was expected to compensate for the undocumented `threads_user_id`, but it merely restates the parameter name ('Threads user ID'), adding no meaning about how the ID should be obtained or formatted. The `response_format` parameter is described in the schema but not in the description, so total value added is minimal.

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 states a specific verb ('Checks') and resource ('publishing rate limit usage for Threads'), making the purpose immediately clear. The 'for Threads' qualifier distinguishes it from the closely related sibling meta_check_instagram_publishing_limit, though it never names that sibling explicitly.

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?

There is no guidance on when to invoke this tool, such as checking limits before publishing to avoid throttling, nor any reference to alternatives like meta_check_instagram_publishing_limit. The agent must infer context from the name alone.

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