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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so safety is covered. The description adds one genuinely non-obvious fact — that uploaded files are not made public — which is useful visibility context, but says nothing about pagination, ordering, or what 'upload status' values look like.

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?

Two short sentences, zero filler, scope stated first and the privacy caveat second. Every clause carries information.

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?

There is no output schema, so the description carries some burden for what is returned — naming 'media, metadata and upload status' partially does this. However, for a read-only listing with no output schema, nothing is said about result size, pagination, or how to interpret upload status, leaving real gaps.

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% for the single 'company' UUID parameter, so the schema already does the documentation work. The phrase 'the company's private guide media' reinforces that all results are scoped to that company, but adds no format or constraint detail beyond the schema. Baseline 3 applies.

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 (list) and resource (private guide media, metadata, upload status) for a given company. It implicitly separates itself from the mutation siblings assets_edit and assets_uploads_create, but never names assets_get, so the read-one vs read-all boundary is left to the agent.

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?

No sentence says when to call this versus summer_assets_get or the upload tools, and no prerequisites or exclusions are given. The agent must infer list semantics from the tool name alone.

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