add_perspective

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

No annotations are provided, so the description carries the full burden. It mentions that a perspective is created and shows a subset, but does not disclose side effects, whether it is a mutating operation that changes the model, what the created perspective initially contains, or if it persists. It adds some workflow context but lacks behavioral depth.

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 sentences, no fluff. It front-loads the action, provides a concrete example, and immediately points to the companion tool for the next step.

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 simple 2-parameter create tool, the description covers the purpose, gives an example, and explains how to populate the perspective via add_to_perspective. It lacks mention of return values or deletion, but no output schema is provided and the workflow is clear enough for an agent to select and invoke it correctly.

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 0%, so the description must compensate. It indirectly clarifies the 'name' parameter by calling the perspective 'named', but it does not explain 'sessionId' at all. Since name is the key semantic parameter and the description gives some context, it is minimally acceptable but not thorough.

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 specific verb ('Create') and resource ('perspective'), and differentiates it from related tools by explaining it creates a named, focused view over a subset of tables/columns/measures. It also distinguishes from sibling add_to_perspective by directing users there for adding members.

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?

It tells when to use the tool (to create a perspective) and directs to add_to_perspective for adding members, which is a clear alternative. However, it does not explicitly say when not to use it (e.g., if only adding members is needed) or mention prerequisites like an open session.

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