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

With no annotations, the description carries the full burden of behavioral disclosure. 'Add' implies a mutation, which is clear, but it does not mention side effects, idempotency, required permissions, or what happens on duplicate names. It provides minimal but non-misleading information, hence a moderate score.

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 a single, compact sentence that front-loads the core action. It is efficient and to the point, though it omits necessary detail for completeness, which does not diminish conciseness.

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?

The description is severely incomplete for a tool with 9 parameters, no annotation, and no output schema. It does not list or hint at the parameters, their valid values, or any constraints. An agent cannot reliably construct a correct request beyond providing a name, making this description inadequate.

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 0%, so the description must compensate, but it only vaguely refers to 'optional known traits' without enumerating or explaining any of the 9 parameters. It adds no detail about formats, allowed values, or which fields are essential beyond the required name, leaving the agent with insufficient guidance.

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 the verb 'add' and the resource 'a person,' making the tool's purpose clear. It also mentions 'optional known traits,' which hints at the optional parameters. While it doesn't explicitly differentiate from siblings, the only creation tool among them, so it is 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?

No guidance is provided about when to use this tool versus the sibling tools (e.g., get_profile, list_profiles). The description implies usage for adding a person, but does not state exclusions or alternatives, leaving the agent to infer the appropriate context.

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