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

Beyond the annotations, the description discloses important behavior: environment variable values are stored in defaultValue, never shown to the model, referenced via {{var:VARIABLE_ID}}, excluded from variablesIds, and masked in responses. It also explains the placeholder workflow for keeping secrets out of chat, which is materially useful for safe invocation.

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 purpose and key semantics are front-loaded, and most sentences carry useful information. The dashboard walkthrough for entering a real secret is somewhat verbose, but it is practical and security-relevant rather than filler.

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 the lack of an output schema and the nested variable object, the description supplies enough detail about creation behavior, field shape, AI-vs-env variable handling, and env masking. An agent can call this tool correctly without needing additional documentation.

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%, and the input schema only defines agentId plus a generic variable object. The description compensates by enumerating the variable object's typical fields—key, type, defaultValue, description, in (body|query|header|path), required, isEnv, isGlobal—and explains defaultValue and env behavior.

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 opens with a specific verb and resource: "Add a variable to a Convocore agent." It clearly distinguishes creation from sibling operations such as update_agent_variable, delete_agent_variable, and list_agent_variables by naming the action directly.

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?

It gives clear operational guidance for AI inputs, optional defaultValue behavior, environment variables, and secret placeholders. However, it does not explicitly compare this tool to update_agent_variable or list_agent_variables, so the agent must infer that this is for new variables rather than modifications or reads.

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