create_profile

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

With no annotations, the description carries the full burden and does disclose meaningful behaviors: INSERT-only write semantics, UNIQUE constraint error on duplicate names, and a SQLite type caveat for config.filePath. It does not mention auth requirements or return behavior, but the disclosed traits go well beyond the tool's name.

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 terse sentences with no filler: purpose, error/alternative, and a parameter caveat are all front-loaded. The trailing [group: profiles] tag adds navigational context without bloating the description.

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?

Despite being concise, the tool has 8 parameters, required nested config, and no output schema. The description covers uniqueness and one config caveat, but an agent would still lack enough detail to correctly construct config, assign role/permissionMode, or understand the result of the insert.

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 only 13%, yet the description adds only one parameter-level hint about config.filePath. It does not clarify the meaning or expected shape of the required name, type, and config parameters, nor the behavioral impact of fields like role, permissionMode, enabled, or tags. Low schema coverage demands far more compensation.

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—creating a new profile row in profiles.db—and explicitly marks it as INSERT-only. It also distinguishes itself from update_profile for existing profiles, making the tool's purpose unambiguous.

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 explicitly tells the agent to switch to update_profile when a profile with the same name already exists, and clarifies that this tool is only for inserts. This provides clear when-to-use and when-not-to-use guidance.

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