embed_manual_in_3mf

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

With no annotations, the description carries the full burden, and it discloses only the entitlement gate. It never says this is a write operation that produces a new file at output_path, whether an existing output is overwritten, what 'signed manifest' means (whose key, what verification), or what a failure looks like.

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 purpose is front-loaded in the first clause, but three of four sentences restate the same Business tier gate and include a marketing upgrade URL with tracking parameters. That is roughly half the text spent on sales copy rather than tool behavior.

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 six-parameter file-mutating tool with no annotations and no output schema, the description omits overwrite semantics, signing requirements, expected failure modes, and any parameter guidance. The only substantive context is the paywall notice.

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?

Six parameters with 0% schema description coverage, and the description explains none of them. The relationships that matter — pdf_path vs manual_id vs release_id vs spec_json_path, and which are optional or mutually exclusive — are left entirely undocumented in both the schema and the prose.

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?

Names a specific verb and resource: augment a 3MF file with an assembly manual plus a signed manifest. That is materially clearer than a bare name restatement, but it never distinguishes itself from nearby siblings such as generate_assembly_manual or diff_assembly_manuals, so an agent cannot tell which one to pick from the description alone.

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?

'Requires Kiln Business' gives a hard precondition, which is genuine usage guidance, but there is no statement of when to use this versus generating a manual or diffing manuals, and no note on whether the source 3MF must be pre-existing or what happens when the manual is missing.

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