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

Annotations declare it is a non-read, open-world, non-idempotent operation, and the description adds the mechanism: the file travels directly from the user's browser to thenewengineer.com and the agent never sees it, plus the token-return flow and a prototype size limit. That is meaningful behavioral context beyond the 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?

Front-loaded with what the tool does, then the trigger condition, then the follow-up sequence. Paragraphs are short and each one carries distinct, non-redundant information; nothing is filler.

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?

With no input schema fields and no output schema, the description compensates by explaining the token handoff and the fallback path, which is exactly what an agent needs to complete the upload workflow. No gaps remain for correct invocation.

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 takes zero parameters, so the baseline is 4. The description still explains the indirect data flow it produces (an upload_token returned for use with read_ifc_networks / ifc_upload_result), which is the closest thing to parameter semantics this call has.

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?

States a specific action and resource: it opens an in-conversation upload box for IFC building-services models (.ifc). It explicitly scopes the file types (HVAC, plumbing, heating) and clearly differs from sibling tools like read_ifc_networks and ifc_upload_result, which it names.

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?

Gives explicit activation conditions: 'CALL THIS when the user wants to analyse an IFC model and has not yet given you a link.' It then sequences the follow-up (read_ifc_networks with the token) and the fallback (ifc_upload_result with upload_token) when no message arrives, so both when and when-not are covered.

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