ora_human_create

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

No annotations provided. Description mentions persistence ('propre memoire') and evolution over sessions, but does not disclose side effects, authentication needs, rate limits, or behavior on duplicate names.

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 sentences, each serving a distinct purpose: core action and contextual behavior. No wasted words.

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?

Covers creation and basic behavior (persistence, evolution), but lacks details on return value, required context (e.g., session), and constraints like name uniqueness.

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 100% for all 3 parameters. The description adds minimal beyond schema; it hints at 'nommee' for name and 'personnalite' for personality, but does not provide new details.

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?

Description clearly states the tool creates a new named personality (human). Verb 'creer' and resource 'personnalite' are specific. Sibling tools like ora_human_evolve modify existing personalities, so creation is distinct.

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?

No guidance on when to use this tool vs alternatives (e.g., ora_apply_template or ora_human_activate). No context about prerequisites or when creation is appropriate.

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