List BIM Plans

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

Annotations already indicate read-only, safe, idempotent operation. The description adds details beyond annotations: 'Returns a paginated JSON array', 'response includes pagination metadata', and mentions pagination control parameters. No contradictions found.

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 five sentences covering purpose, usage, response details, required parameter, and API endpoint. No extraneous information; 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?

For a list tool with no output schema, the description adequately explains pagination and response metadata. It identifies required parameters and mentions filtering. Could benefit from mentioning that results are scoped to the project, but overall complete given annotations and schema.

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% with detailed descriptions. The description adds context by stating 'Required parameters: project_id' and explaining usage of page/per_page for pagination and 'filter by query parameters' for filters, exceeding the baseline of 3.

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 'Lists BIM Plans associated with the specified Project' with a specific verb and resource. It distinguishes from sibling tools by mentioning 'paginated overview' and 'filter by query parameters', which is unique among many list tools.

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 tells when to use the tool: 'Use this to enumerate BIM records when you need a paginated overview, to find IDs, or to filter by query parameters.' It also identifies the required parameter. However, it does not explicitly state when not to use it or compare to alternatives like list_bim_model_revision_plans.

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