intake_engineering_drawing

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

No annotations exist, so the description carries full burden. It does disclose the Kiln Business entitlement requirement, which is valuable, but it says nothing about duplicate registrations, unsupported file types, permissions, or side effects. Worse, the middle paragraph describes capabilities ('would check the extracted requirements... prepare recommendations for the quote') that this tool does not perform, which can mislead an agent about its behavior.

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 one-line purpose is well front-loaded, but three of five lines are pricing/upsell copy and a marketing URL that do not help an agent invoke the tool. The description is padded rather than tight.

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 mutation tool with no annotations, no output schema, an undocumented required file_path, and an unclear return shape ('pages'), the description leaves the agent without enough to call it correctly or know what follows. It also never names the natural next step (e.g. submit_drawing_extraction).

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 50%, and the only documented parameter's description is 'Default: \"\"', which conveys almost nothing. The description never mentions file_path (required) or material, so it adds no meaning about accepted formats, path conventions, or how material affects intake.

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 first sentence gives a specific verb and resource: 'Start a drawing intake: register the drawing and get its pages to read', which tells an agent both the mutation (register) and the return (pages). It does not name or contrast itself with near siblings such as submit_drawing_extraction or assess_drawing_manufacturability, so it stops short of full differentiation.

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?

'Start' implies this is the entry point of a drawing workflow, and the mention of checking extracted requirements hints at a later stage, so sequencing is implied. However, no alternative tool is named and no explicit when-not condition is given; the remaining lines are tier/upsell copy rather than usage guidance.

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