show_allviews

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

Description discloses that it lists cross-module views including default and saved, but omits behavioral traits such as being a read-only operation, pagination behavior, or any side effects. Since no annotations exist, the description carries full burden and falls short.

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?

One sentence plus a note, very concise and front-loaded with the action verb. No unnecessary words.

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?

Description covers what the tool lists and the key prerequisite (model ID), but lacks detail on output format, sorting, pagination, or what 'cross-module' means. For a list tool with 4 parameters and no output schema, it is moderately complete.

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 has 100% description coverage, so baseline is 3. Description adds overall context about view types but does not add parameter-specific meaning beyond the schema, which already includes details like using show_models for modelId and search as case-insensitive substring.

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 clearly states verb 'List' and resource 'all views in a model', specifying scope as cross-module including default and saved. This distinguishes it from siblings like show_savedviews and show_viewdetails.

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?

Description mentions requirement for model ID and that name resolution is not supported, implying need to use show_models first. However, it does not explicitly state when to use this tool versus alternatives like show_savedviews for only saved views.

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