vivado_source_tcl

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

No annotations provided, so description carries full burden. It mentions a security requirement but fails to disclose side effects, error behavior, return values, or destructiveness. The 'expect_destructive' parameter hints at potential issues, but the description does not address them.

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 sentences, no fluff. Front-loaded with purpose. Every word adds value.

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?

Despite having an output schema and 5 parameters, the description is extremely sparse. It does not explain what sourcing does, how timeout or destructive behavior are handled, or what output is returned. Incomplete for a tool with moderate complexity.

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 description coverage is 0%, so description must compensate. However, it does not describe any of the 5 parameters (session_ref, script_path, tclargs, timeout_seconds, expect_destructive). Only 'source a Tcl file' loosely maps to script_path, but no semantic detail beyond the schema.

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 the verb 'source' and the resource 'Tcl file in a managed session'. It distinguishes from sibling 'vivado_run_tcl' by specifying file sourcing rather than inline commands. The requirement 'trusted-local or unrestricted profile' adds context.

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?

Specifies a prerequisite (trusted-local or unrestricted profile) but lacks explicit guidance on when to use this tool vs alternatives like 'vivado_run_tcl'. No when-not or alternative tool references.

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