listViewpoints

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

Annotations already disclose the key safety traits (readOnlyHint=true, destructiveHint=false, idempotentHint=true). The description adds the useful 'current page' scope but does not go beyond that to describe behaviors like empty result handling, ordering, or pagination. With annotations present, this is adequate but not rich.

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 two sentences: one functional statement and one return signature. There is no fluff or redundancy; it is efficiently front-loaded with the core purpose.

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 read-only, idempotent tool with one optional parameter, rich annotations, and an output schema, the description is sufficient. It clarifies the scope ('current page') and the return envelope, and no further behavioral or safety details are necessary.

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 100%: the only parameter sessionId is fully described in the input schema. The description adds no additional parameter semantics, but with full schema coverage the baseline of 3 is appropriate.

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 states a specific verb and resource: 'List camera viewpoints saved in the current page.' This clearly distinguishes the tool from siblings like saveViewpoint/loadViewpoint and getView/setView by scoping to saved viewpoints and the current page.

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?

The purpose implicitly suggests when to use the tool (to enumerate saved camera viewpoints), but there is no explicit when/when-not guidance or mention of alternatives. The 'current page' scoping provides some context but no direct comparison with related sibling tools.

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