list_lightboxes

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

No annotations exist, and the description only says 'List lightboxes in the organization' with no mention of pagination, read-only nature, ordering, or any behavioral nuances. The domain-specific behavior (e.g., parent_id filtering) is not disclosed.

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?

A single, concise sentence conveys the core purpose without wordiness. Every word 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 annotations, no output schema, and an undocumented parameter, the description alone is insufficient for an agent to fully understand the tool's behavior, expected parameters, or return value. It lacks context about pagination semantics and parent_id usage.

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?

The schema describes 'page' and 'per_page' but leaves 'parent_id' undocumented. The description adds no parametric context, failing to compensate for the 67% schema coverage gap, especially for parent_id.

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 clearly states the action ('List') and the resource ('lightboxes'), with an organizational scope. It distinguishes from sibling tools like get_lightbox (single item) and create_lightbox/delete_lightbox (mutations).

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?

The verb 'List' implies enumeration, and sibling names provide some context, but there is no explicit guidance on when to use this versus get_lightboxes_tree or get_lightbox. No alternatives or exclusions are mentioned.

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