company_content_assets

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

No annotations are provided, and the description does not clarify whether the tool is read-only or mutating, what side effects it may have, or what evidence is retained and how it is exposed. The term 'operate' implies action but without detail.

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, short sentence, which is concise in length, but it omits essential details and front-loads abstract terminology rather than concrete functionality. It is not effectively structured for quick understanding.

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?

Despite having an output schema, the description provides no context about the tool's domain, operations, or expected inputs. Within a large family of company_* tools, this description is insufficient to understand its unique role or how to interact with it.

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?

All six parameters (project_id, bundle_json, payload_json, now, operation, entity_ref) lack any description. The schema coverage is 0%, and the description does not hint at their expected values, formats, or roles, making it impossible to construct a correct call.

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 uses vague business jargon ('durable content lifecycle', 'retained host and provider evidence') without specifying any concrete operations like list, create, or update. It does not distinguish this tool from sibling tools such as company_content_library or company_memory, making its purpose ambiguous.

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 on when to use this tool versus alternatives. The description does not mention any preconditions, typical use cases, or relationships with other company_* tools, leaving the agent without context for selection.

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