section.add_user

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

No annotations are provided, so the description carries full burden for behavioral disclosure. It fails to state any side effects, permissions needed, whether the operation is reversible, or what happens on failure. The description is essentially a tautology of the tool 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?

Extremely concise (3 words), but this is under-specification, not efficient communication. No structure or front-loading of key information. The description fails to earn its place by being helpful.

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?

With 8 parameters, zero schema coverage, no output schema, and no annotations, the description is critically incomplete. It neither explains the tool's purpose nor how to use the parameters. The context signals highlight high complexity, yet the description offers minimal guidance.

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%, meaning no parameter descriptions exist in the schema. The description does not explain any of the 8 parameters (e.g., what 'align', 'semantics', 'type_name', 'entry_size' mean). Three letter description does not compensate for zero schema coverage, leaving agents guessing.

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 "Add user section." is vague. It does not specify what exactly is being added (a section in a user context?), what a "user section" means, or how it relates to the tool name. The tool name section.add_user suggests adding a user to a section, but the description reverses this ("Add user section"), creating confusion. No differentiation from sibling tools like segment.add_user or section.remove_user.

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., segment.add_user, section.remove_user). No mention of prerequisites, workflows, or when not to use it. The description provides zero usage context.

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