Ouvrir le formulaire de création BCF

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

No annotations provided, so description carries full burden. Discloses interactive form behavior, optional prefilling, and capability to attach current 3D viewpoint via viewer bridge. Does not mention auth or rate limits but for a form tool, the main behavioral traits are covered.

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?

Three sentences, front-loaded with main purpose. Every sentence adds value (purpose, prefilling note, viewpoint attachment, alternative). No wasted words.

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 complexity (7 params, no output schema, no annotations), description explains the interactive form nature, optional prefilling, viewpoint attachment, and distinguishes from sibling. Covers all relevant aspects for a creation-form tool.

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 baseline is 3. Description adds context that parameters are optional prefilled fields, but does not significantly extend beyond schema descriptions.

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 it shows an interactive form to create a BCF topic, with specific verb 'Show an interactive MCP App form' and resource 'Trimble Connect BCF topic'. Distinguishes from sibling tc_bcf_create_topic by noting alternative for direct creation.

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?

Explicitly describes when to use (user wants to create via form) and provides alternative (use tc_bcf_create_topic + tc_create_viewpoint_from_viewer for direct creation). Lacks explicit 'when not to use' but the alternative serves as guidance.

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