get_current_view_info

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

No annotations provided, so description must carry the burden. It describes return values but omits potential side effects (unlikely) or error conditions (e.g., if no view is active). The 'get' verb implies read-only, but this is not confirmed. Misses explicit safety guarantees.

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?

Two concise sentences followed by a bullet list of seven items. Every line adds information without repetition or fluff. Front-loaded with the primary 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?

Given no output schema, the description adequately explains return values with a detailed list. However, it does not cover prerequisites (e.g., an open document) or potential errors. For a simple read tool, this is mostly sufficient.

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?

No parameters exist, so baseline is 4. The description adds value by listing returned fields, which compensates for the absence of an output schema. No parameter details 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?

Clearly states the action ('get') and the resource ('detailed information about the currently active view'), which distinguishes it from sibling tools like get_revit_view (needs a view ID) and list_revit_views (lists all views). The verb+noun structure is specific.

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?

Implicitly distinguishes usage by specifying 'currently active view', indicating no parameter required. Does not explicitly state when not to use, but the context (no parameters, sibling tools) makes it clear. Lacks explicit exclusions or alternative recommendations.

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