profiles_stats

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

Annotations already declare readOnlyHint=true, and the description adds context: snapshots are captured ~23h daily, and stats fields are platform-native (not normalized). This extra detail helps the agent understand data freshness and structure, going beyond the annotation.

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?

Description is three sentences, front-loading the main purpose. Each sentence adds value (timeseries nature, snapshot frequency, platform-specific behavior). No unnecessary repetition.

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?

The description explains the output (daily snapshots, native stats) and key conditional parameter behavior. Without an output schema, this provides sufficient context for usage. Some details like pagination are omitted but not critical for this 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?

Schema coverage is 100%, so baseline is 3. The description adds significant meaning by clarifying when placement_id is required vs optional, and instructing where to get it. This helps the agent differentiate parameter usage across platforms.

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?

Description clearly states 'Get the follower/engagement timeseries for a profile' with a specific verb and resource. It distinguishes from sibling tools like post_stats (a different resource) and profiles_list (which lists profiles).

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?

Description provides explicit guidance on when to include or omit placement_id based on platform (required for facebook/linkedin/telegram). It also references the sibling tool profiles_placements to obtain the value. However, it does not discuss when to prefer this tool over alternatives like post_stats for post-level data.

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