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

Discloses key behaviors beyond the readOnlyHint annotation: secret values are always masked, personal variables override organization and environment variables, and they are visible only to the user. Also mentions the requirement for organization 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?

Three concise sentences with zero fluff. Core purpose is front-loaded, followed by usage guidance and behavior notes. Every sentence contributes 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?

Complete for a simple list operation with two parameters and no output schema. Covers purpose, usage, behavioral nuances, and context requirements. Nothing an agent needs to call it correctly is missing.

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% (both projectId and environmentId have descriptions). The description adds no extra parameter-specific detail, but neither is any needed; baseline of 3 is 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?

Clearly states what the tool does: lists personal variables for one environment. Highlights distinguishing traits (overrides org/env variables, visible only to you) and differentiates from sibling tools like resolve_variables.

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 provides when-to-use guidance ('Use this for your own layer') and names the alternative for the merged result ('for the merged result of all three use resolve_variables'). Also notes the organizational context requirement.

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