llm_import_profile

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

Describes merging and validation behavior, and default source. No annotations provided, but the description adds some behavioral context. However, it doesn't cover all aspects like reversibility or authentication requirements.

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?

Extremely concise: one-sentence summary, then structured Args and Returns. No wasted words, front-loaded with purpose.

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 only one optional parameter and an output schema provided, the description covers the essential aspects: param meaning, validation rules, default behavior, and return value summary.

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 only parameter 'url' is explained as an optional URL to a profile JSON file with a default to community latest, adding meaning beyond the schema's bare type and default.

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?

Clearly states it imports a learned routing profile from community or URL, distinct from sibling tools like llm_share_profile and llm_set_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?

Implies usage for importing shared profiles, with strict validation (confidence >= 2). No explicit when-not or alternatives, but context from sibling tools provides some guidance.

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