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

No annotations are provided, so the description carries the full behavioral burden. It does disclose that a purpose is mandatory and logged per call and implies a read-only report ('get'), plus a cost comparison, but it omits permission/auth requirements, whether the report is cached or live, and any rate or size limits. The purpose-logging rationale partially duplicates the schema description rather than adding new context.

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 short sentences with zero waste; the scope (the whole picture) is front-loaded, followed by the cost argument and the one hard requirement. Every sentence earns its place.

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, the description compensates well by enumerating the six content areas the report returns, so an agent knows what to expect. Combined with the 100%-covered input schema and the stated purpose/fee behavior, only the absence of read-only/auth framing and response shape details keeps it from being fully complete.

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 100% — code, screen, purpose and interpret are all documented with format, enum values and fee implications in the schema itself. The description only restates the purpose requirement and its rationale, adding no format or semantic detail beyond what the schema already supplies.

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?

States a specific verb and resource ('One call returning the whole picture') and then enumerates the exact contents — profile, participants, beneficial owners, real property, seizure acts, court cases — which map directly onto the sibling tools (get_participants, get_beneficial_owners, get_real_estate, get_seizures, get_court_cases). An agent can tell this is the bundle alternative to those individual calls without opening any schema.

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?

'Cheaper than the parts bought separately' is a concrete reason to prefer this tool over composing the sibling getters, which gives clear usage context. It stops short of naming alternatives or stating when not to use it (e.g. when only beneficial owners are needed, or when create_kyc_package / lookup_company is the better entry point).

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