List BIM Model Revision Viewpoints

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

Annotations already provide readOnlyHint, destructiveHint, idempotentHint. The description adds valuable behavioral details: returns paginated JSON array, pagination control via page/per_page, and pagination metadata. No contradictions with annotations.

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 four sentences, front-loading the purpose and key usage. It includes essential details (pagination, required params, API endpoint) without unnecessary verbosity. Every sentence adds value.

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 tool's complexity (9 parameters, no output schema), the description covers the core functionality, pagination, and required parameter. It provides an API reference. It could potentially explain the concept of viewpoints or relationships, but it's sufficient for a list tool with good annotations.

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%, so the baseline is 3. The description mentions required parameter project_id and pagination parameters (page, per_page) but does not add significant meaning beyond what the schema already provides. No additional semantic value for other parameters.

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 clearly states the verb "List" and the specific resource "BIM Model Revision Viewpoints." It provides usage context like enumerating records, finding IDs, or filtering. The tool name is self-explanatory and distinguishes from sibling tools that create, delete, or bulk operate on the same resource.

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 description explicitly says when to use the tool: for paginated overview, finding IDs, or filtering. It does not mention when not to use it or alternatives, but the context is clear enough. Given sibling tools are mostly mutations, the list tool is unique, so no explicit exclusion needed.

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