get_assembled_code

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

No annotations provided; description clarifies it returns processed code rather than raw file, but lacks details on side effects (e.g., does it trigger compilation?) or performance impact. Still, it adequately discloses its behavior for verification purposes.

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 plus a concise bulleted list; front-loaded with purpose and efficient use of words, no redundancy.

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?

Given no output schema, the description returns the expected content type (Vue SFC or PHP class) and hints at its structure, which is sufficient for a verification tool. Could mention if there are limitations or size constraints.

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 covers the 'uuid' parameter with a description; the tool description adds minimal extra meaning beyond 'UUID of the file', so baseline score applies.

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 description clearly states the tool retrieves assembled source code for a file, specifically Vue SFC or PHP class as rendered, distinguishing it from sibling get tools that likely return raw file contents.

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 advises using after save_file for verification, with a bulleted checklist of what to check, providing strong contextual usage guidance.

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