get_post_insights

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

No annotations are provided, and the description does not disclose whether this is a read-only operation, whether permissions are needed, how date ranges are handled, or what the response format is. The word 'Get' implies read-only, but it is not explicitly stated, and no other behavioral context is given.

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 brief, which is concise, but it sacrifices necessary substance. For a tool with no annotations and an uninformative schema, this brevity is under-specification rather than good conciseness.

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?

With no output schema, no annotations, and a vague description, the agent is left without enough context to select and invoke the tool correctly. It does not specify what metrics are returned, whether historical data is included, or how errors are handled.

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 adds no meaning for the parameters 'from', 'to', or 'account_id'. It is unclear if 'from'/'to' are date ranges, what format they expect, or how 'account_id' selects the account. The parameter names are mildly self-explanatory but the description does not confirm or explain them.

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 says 'Get detailed performance metrics' – it identifies a verb and a general resource (metrics) but does not specify the entity (post, account) or the kind of metrics. The tool name suggests post insights, but the description alone is ambiguous and does not distinguish it from other analytics-related siblings like get_best_times.

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 about when to use this tool versus alternatives such as get_post, get_best_times, or list_posts. It does not mention use cases, prerequisites, or exclusions.

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