create_brand_profile

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

Beyond the annotations, the description discloses that profiles are stored locally under ~/.raven/creative by default and that the tool both creates and updates profiles. This adds useful side-effect context. Nothing in the description contradicts the destructiveHint annotation; 'update' reasonably implies possible overwrite behavior.

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?

Two short sentences deliver the action, resource, purpose, key stored fields, and the default storage location. There is no filler or repetition of annotations, and the primary statement is front-loaded.

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 full schema coverage, a single required parameter, and the absence of an output schema, the description is sufficient for an agent to invoke the tool correctly. It provides the storage default and purpose, though it could theoretically add more detail about update/overwrite semantics or the response shape.

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 input schema has 100% description coverage for all parameters, so the schema already carries the semantic load. The description's field list mostly mirrors what the schema already documents rather than adding deeper parameter-level meaning. This is the expected baseline when schema coverage is high.

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 states a specific action ('Create or update') and a clear resource ('local brand profile used by Raven creative jobs'), then lists what the resource stores. This makes it easy to distinguish from read/list siblings like get_brand_profile or list_brand_profiles, and from create_character_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 gives clear context: this is for creating or updating a local brand profile for Raven creative work. It does not explicitly name alternatives or state when not to use it, so it stops short of the strongest possible guidance, but the intended context is still clear.

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