perspective_upsert_view

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

Indicates 'Mutating' so the agent knows it changes state, but no details on what exactly is mutated (create, update, both?), whether it is destructive, required permissions, or side effects. With no annotations, the description should provide more behavioral context.

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?

Extremely short but at the cost of clarity. It is under-specification, not conciseness. The description does not front-load useful information.

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 the complexity (4 params, nested objects, output schema exists), the description is completely inadequate. It fails to explain the tool's purpose, behavior, parameter details, or output format.

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?

Description adds no meaning to the parameters. With 0% schema description coverage, the description should compensate but gives no information about the role, constraints, or format of parameters like confirm, project, view_json, view_path.

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 'Mutating, bridge plane + REST scan' is cryptic and fails to state what the tool does. The name suggests upsert (create/update) of a view, but the description does not clarify the resource or action, and does not distinguish it from sibling tools like perspective_get_view or perspective_delete_view.

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 on when to use this tool vs alternatives. The description provides no context about suitable scenarios, prerequisites, or when not to use it.

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