prompt_add_variables

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

With no annotations, the description carries the full burden of explaining behavior, but it only says 'Add' without mentioning side effects, files created or modified, API key usage, permissions, or return behavior. An agent cannot predict what invoking this tool will change.

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 description is short but not usefully concise because it omits essential information. A single vague sentence does not earn its place, as it delivers almost no actionable signal.

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 two parameters, no annotations, and no output schema, this description is completely inadequate. An agent lacks enough information to call it safely or correctly, including what input is needed and what a successful result looks like.

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?

The schema documents directory as 'Project directory' but leaves api_key without a description, and the description does not clarify either parameter. It fails to explain how directory relates to the variable system or what api_key is for.

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 'Add template variable system' essentially restates the tool name without explaining what a template variable system is, what it does, or where it is applied. It also fails to distinguish this tool from siblings like prompt_create_templates or prompt_add_versioning.

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?

No guidance is given about when to use this tool, what problem it solves, or when a sibling tool would be more appropriate. The description provides no context, prerequisites, or alternatives.

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