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

Annotations already declare readOnlyHint, idempotentHint, and non-destructive behavior, while the description adds useful context about ordering, returned fields, drop page defaults, output completeness, and pagination. There is minor ambiguity around page/limit values, but no annotation contradiction.

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 front-loaded with purpose and packed with relevant guidance, with no filler sentences. Some dense parenthetical pagination detail slightly reduces immediate clarity, but each sentence mostly 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 still covers key return fields (filename and time added), pagination behavior, and the completeness indicator. It could be more complete about limit constraints and asset identifiers, but it is adequate for a three-parameter list tool.

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 33%, with offset alone documented in the schema; the description usefully explains drop_session_id and offset pagination, plus references public_url as an output field. Limit semantics remain vague and somewhat in tension with the schema: the schema has default 10 and maximum 50, while the description mentions up to 20 per drop page and 'offset + limit up to 1000' without reconciling these values.

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: list the newest media assets for the authenticated user, with drop-specific usage via drop_session_id. It does not explicitly contrast with similar siblings such as list_posts or list_google_business_media, so sibling differentiation is incomplete.

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?

It gives clear conditions: after create_media_drop, pass drop_session_id; use public_url with validate_post / create_post; page with offset when the output says not all matching files are shown. It lacks explicit when-not guidance or a direct named alternative listing tool.

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