List drops

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

Discloses pagination, ordering, field set, and the distinction between drop_ id and slug/URL. Also reveals authorization caveat for workspace ('delegated credentials only') and the recovery use-case for domain. These go well beyond the readOnlyHint annotation.

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?

Concise yet packed with value: opens with the core function, then usage, then crucial ID semantics, then parameter-specific guidance. Every sentence earns its place without redundancy.

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?

For a list tool, it covers ordering, pagination, return fields, parameter meanings, and related tool references. With an output schema present, the description fully supports selection and invocation.

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?

Even with 100% schema coverage, the description enriches each parameter: limit/cursor are implied, domain is explained as a recovery path, and workspace is detailed with id/slug format, delegated credentials, and as the read-side twin of publish's workspace.

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?

Description states a clear verb and resource: 'List the account's drops' with specifics on ordering (newest first), pagination, and returned fields. It distinguishes from siblings by explaining the drop_ id relationship to mutating tools and referencing domain/workspace list tools.

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?

Explicitly states when to use: 'Use when the user wants to list / show my drops / see what they have published.' Provides parameter usage context (domain, workspace) and references related tools, but does not explicitly mention when not to use or name alternative tools for similar operations.

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