get_best_times

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

With no annotations, the description carries full burden. It discloses that the tool works for a single connected account, requires the Professional plan, and uses UTC timezone. It does not mention read-only status, rate limits, or what happens with insufficient engagement history.

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?

Three sentences, each adding value: purpose, plan requirement, and usage guidance with timezone. No redundancy or irrelevant information. Front-loaded with the core function.

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 tool's simplicity (one parameter, no output schema), the description covers purpose, constraints (plan, timezone), and a usage hint. Lacks explicit return format, but is largely complete for a tool that likely returns a list of times.

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 coverage is 0%, so description must explain the parameter. It mentions 'one connected account,' implying account_id identifies the account, but does not explicitly state that it comes from list_accounts or provide examples. Adequate but not explicit.

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 personalized best posting times for a connected account, based on engagement history. It distinguishes from broader analytics tools like get_account_analytics. However, it does not specify the exact format of the output (e.g., list of times), which slightly reduces clarity.

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 gives a usage hint: 'Use it to pick scheduled_for.' This implies the tool is meant to be used before scheduling posts. However, it does not explicitly contrast with alternatives like get_account_analytics or mention when not to use this tool.

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