update_me

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It only mentions 'update profile info' but doesn't clarify whether it's a partial update, whether fields are validated, if authentication is required, or any side effects. The agent is left uninformed about how the tool behaves beyond the basic action.

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 very short and arguably concise, but it is under-specified rather than efficiently complete. It lacks structure, such as bullet points or examples, and provides little beyond what the tool name already implies. It is not verbose, but it also doesn't earn its place by adding meaningful context.

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 7 parameters, no schema descriptions, no annotations, and no output schema, the description is severely inadequate. It doesn't explain return values, handling of omitted fields, or any constraints. The tool appears complex, but the description provides almost no contextual information, making it impractical for correct invocation.

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 has 0% description coverage, and the description adds no meaning to the 7 parameters. Fields like 'vertical' and 'websites' are ambiguous, and the description does nothing to clarify their purpose or format. This is a critical gap for an agent to correctly populate parameters.

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 'Update profile info' uses a clear verb and resource, indicating it modifies user profile data. It is distinct from sibling tools like get_me (retrieval) and update_calling_settings (specific settings). However, it doesn't specify which profile fields or distinguish from potential other update tools, so slightly more specificity would improve it.

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?

The description provides no guidance on when to use this tool versus alternatives, no prerequisites, and no exclusions. It simply states the action without context, leaving the agent without direction on appropriate usage.

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