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

Beyond the annotations, the description discloses crucial behavior: the tool is tokenless, consumes a daily extension payload, derives findings such as admin without 2FA and stale invites, and raises a meta_access_risk alert on a new high-risk finding of a previously audited profile. It also explains the replace-snapshot semantics with 'The payload is the whole picture — grants missing from it are removed,' which is essential context for a non-read-only, non-idempotent operation.

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 purpose and tokenless scope are front-loaded, and the dense single-sentence payload description is followed by the important alert and replacement semantics. It is appropriately sized for a complex ingestion tool, though the long opening sentence could be split for readability.

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 nested-object tool with no output schema, the description covers the data source, the payload contents, the derived risk findings, and the alert side effect. What is less clear is what the tool returns or confirms after ingestion, but the operational behavior needed to invoke it is otherwise well covered.

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?

With only 33% schema description coverage, the description compensates by explaining the meaning and contents of the main payload sections: BM people with role, two-factor status and pending invites, plus assigned users and partner businesses on ad accounts, pages and pixels. It does not explain the warnings array or explicitly map every top-level parameter, but it adds substantial meaning beyond the schema snippets.

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 states a specific verb and resource: report the access picture of every Business Manager a logged-in FB user belongs to, including BM people and ad account/page/pixel assignments and partners. It distinguishes itself from Graph-token-based Meta tools by emphasizing 'WITHOUT a Graph token' and ties itself to register_meta_cabinet, though it does not explicitly contrast with the other report_meta_* siblings.

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?

Usage context is implied rather than stated: it is what the Torvex browser extension sends once a day and it lands under the same tokenless profile as register_meta_cabinet. There is no explicit 'use this when' guidance versus alternatives such as register_meta_cabinet or report_meta_cabinet_health, so the agent must infer the call condition.

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