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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so safety is covered. The description adds one genuinely useful behavioral disclosure — that no secret upload capability is returned — but says nothing about error behavior for missing/foreign assets or what the chunk receipts represent.

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 with the read/scope statement front-loaded; the security caveat in sentence two is short and earns its place. Slightly wasteful in that the second clause of sentence one lists outputs rather than telling the agent anything actionable.

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 partially compensates by naming what comes back (checksum, chunk receipts), but for a two-required-parameter lookup it leaves the asset ID semantics and failure modes unexplained, so an agent can invoke it only in the happy path.

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 only 50%: only `company` is documented ("Summer company ID"), while `asset` has just a UUID pattern and no prose. The description offers no clarification of either parameter or their relationship (asset scoped to company), so it fails to compensate for the coverage gap.

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 verb+resource ("Read one guide asset") is specific and the word "one" implicitly distinguishes it from summer_assets_list, but the remainder ("checksum and resumable chunk receipts") reads as output content rather than purpose, and it never names list/edit/upload siblings to differentiate.

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 statement of when to call this instead of summer_assets_list (to browse) or summer_assets_uploads_create/complete (to write), and no prerequisites such as needing an existing asset ID or membership in the company.

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