seed_list_views

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

No annotations are available, so the description must carry the burden of behavioral disclosure. It does state that the tool returns 'metadata' (implying a read-only operation, not destructive), which is useful. However, it does not disclose pagination behavior, response format, or any side effects, leaving notable gaps.

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 a single, concise sentence that directly states the tool's purpose. Every word earns its place with no fluff or repetition.

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?

Given there is no output schema, the description should explain what the return value looks like, but it only says 'metadata' without specifying fields or structure. It also omits pagination details despite the schema having pageSize and pageNumber parameters. The description is too sparse to be fully complete for an agent invoking this 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 description coverage is only 33% (only filtersJson has a description). The description adds no meaning to pageSize, pageNumber, or filtersJson beyond what the schema already provides. Since coverage is below 50%, the description should compensate, but it does not.

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 ('Seed view metadata'), scoped to 'the configured organization'. This distinguishes it from sibling tools like seed_list_frames and seed_list_tables by specifying 'view metadata' rather than view content.

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 guidance is provided on when to use this tool versus alternatives. There is no mention of seed_get_view for retrieving a single view or seed_list_frames for frames, and no exclusion criteria. The description only states the basic action without context.

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