get_revit_model_info

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

The description lacks behavioral details. Since no annotations are provided, the description should disclose traits like read-only nature, data freshness, or potential performance impact. It only states 'get info', which is insufficient for safe invocation.

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 a single sentence, front-loaded, and contains no extraneous words. However, 'comprehensive information' is broad and could be more precise, slightly reducing effectiveness.

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?

Despite low complexity (no params, no output schema), the description is too vague. It does not indicate what specific information is returned, leaving the agent with an ambiguous expectation. A description of the response structure would improve completeness.

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?

The tool has zero parameters, and the schema coverage is 100% (vacuously). Per the calibration guidelines, baseline for 0 params is 4. The description adds no parameter info because none are needed.

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 tool gets information about the current Revit model, using a specific verb and resource. However, 'comprehensive information' is vague and does not distinguish it from siblings like get_revit_status or get_current_view_info, which also provide model-related data.

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 versus alternatives. It does not specify prerequisites, context, or when not to use it. Siblings exist that might be more appropriate for specific queries, but no comparison is provided.

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