show_savedviews

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

Describes the listing behavior, including the includeSubsidiaryViews parameter for unsaved views. No annotations exist, so description carries full burden; it does not mention side effects or auth, but as a read operation, it is sufficiently transparent.

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?

Two short sentences plus a tip, no wasted words. Front-loaded with the main action and key usage guidance.

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?

Lacks description of the return value structure or fields, which is important since no output schema is provided. For a tool used to retrieve view IDs, the response format is relevant context.

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 100% but description adds value by explaining when to use includeSubsidiaryViews and providing a tip that moduleId works as a default viewId, which goes beyond the schema description.

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?

Clearly states it lists saved views in a module, with a specific tip for unsaved subsidiary views. Distinguishes from sibling tools like show_allviews or show_viewdetails by focusing on module-specific saved views.

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?

Provides context on why view IDs are needed (for read_cells) and a tip about moduleId as default viewId. However, does not explicitly specify when not to use this tool versus alternatives like show_allviews.

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