investor_save_profile

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

With no annotations, the description must disclose behavioral traits. It only states it's a save operation and doesn't change broker data. Critical details like whether it overwrites existing profiles, requires authentication, or has side effects are missing.

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 extremely concise with two short sentences. Every word adds value: the first states purpose, the second adds behavioral nuance. No redundancy or 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 schema descriptions and output schema, the description is too brief. It doesn't explain what 'saving' entails (e.g., persistent storage, override behavior), nor does it mention how the profile can be retrieved (e.g., using investor_get_profile). The tool's behavior is under-specified.

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 single parameter 'profile' has no schema description (0% coverage). The description adds no meaning beyond the schema, leaving the agent uninformed about the object structure, required fields, or acceptable values.

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 'Save local investment profile' specifying the action and resource. It also distinguishes from siblings by noting it's local and does not affect broker data, contrasting with tools like investor_get_profile.

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 implies use for local saving without broker sync but does not explicitly state when to use or alternative tools. No direct when/when-not guidance is provided, only an implied context.

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