td_scaffold

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

Describes what the template handles: creation, connector compatibility, naming, layout, first force-cook. Also specifies return structure. Annotations are minimal, so description adds substantial behavioral context.

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 well-structured sentences: first states purpose, second adds usage guidance and return info. 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?

Covers purpose, return value, and usage context. With openWorldHint=true and destructiveHint=false, description is sufficient for a scaffold tool. Could mention side effects on existing network, but not critical.

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% with good parameter descriptions. Description mentions template options but doesn't add meaning beyond schema for parameters like name_prefix or response_format. Baseline 3 appropriate.

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?

Description clearly states verb 'Create' and resource 'complete, pre-wired network from a template'. Distinct from siblings like create_td_node which creates individual nodes.

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 says 'Prefer this over hand-wiring common setups', giving when-to-use guidance. Could mention when not to use (e.g., custom wiring not in templates).

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