Métricas disponíveis

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

With no annotations, the description carries the burden of behavioral disclosure. It transparently frames the tool as a read-only catalog, avoiding any implication of mutating data. Mentioning the map of discontinued metrics and substitutes adds context beyond a simple list, though output format and pagination are not disclosed.

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 a single, well-structured sentence that front-loads the main purpose (catalog of metrics) and adds the key nuance about discontinued metrics. No redundant or filler content is present.

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 low complexity (one optional parameter, no output schema), the description is serviceable but not fully complete. It explains the scope and special feature (discontinued metrics), but omits how the surface parameter affects results and what the catalog entry structure looks like, leaving some ambiguity for an agent.

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 never mentions the 'surface' parameter, so it does not add meaning beyond the schema's enum/default. The description's mention of 'Page e Instagram Insights' loosely aligns with the surface values, but does not explain how to use the parameter to filter the catalog.

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 identifies the tool as a catalog of organic metrics for Page and Instagram Insights, also covering discontinued metrics and their substitutes. This distinguishes it from sibling tools that focus on actual metric values (e.g., page_insights, followers_overview). The purpose is specific and actionable.

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 catalog nature implies use when an agent needs to know available metrics or understand Meta's discontinued metrics and replacements, but no explicit when-to-use or when-not-to-use guidance is provided. It does not mention alternatives by name, relying on the sibling list to convey context.

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