Check Threads Publishing Limits

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

Annotations already declare readOnlyHint=true and destructiveHint=false. The description adds value by specifying the return includes 'current usage and limit quota (250 posts per 24 hours),' which informs the agent of the exact limit and output scope.

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 extremely concise: two sentences, one for purpose and one for parameters/returns. It is front-loaded with the core action and includes structured Args and Returns sections, with 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?

For a simple read tool with no output schema, the description covers the required parameter and return value but omits the optional 'response_format' parameter. This gap makes it partially incomplete, though the core functionality is adequately described.

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 only 50% (only 1 of 2 parameters described in the description). The description merely restates the schema for 'threads_user_id' without additional semantics, and completely omits 'response_format.' With low coverage, the description fails to compensate.

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 it 'Checks the current publishing rate limit usage for Threads.' The verb 'checks' and the specific resource 'publishing rate limit usage' uniquely identify the tool's function. Among sibling tools, none other checks Threads rate limits, so it is well-distinguished.

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 implies the tool is used to monitor rate limit usage before posting, but it does not explicitly state when to use it or suggest alternatives. Given the self-explanatory nature of a rate limit check and no competing sibling tool, the guidance is clear enough.

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