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

Annotations only declare destructiveHint=true; the description adds real value beyond that by flagging 'WRITE', naming the required scope (flex.community.members.create), and citing the underlying endpoint (POST /members). It does not describe side effects, what a partially-successful create does, or rate limits, but the auth/scope disclosure is meaningful behavioral context.

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, front-loaded with the 'WRITE' signal, followed by purpose, scope requirement, and endpoint. Every sentence earns its place with no filler.

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?

For an 11-parameter mutation with a nested object and no output schema, the description covers purpose, auth scope, and endpoint but never says what is returned (e.g., the created member's id), which an agent typically needs after a create. It is adequate but leaves that gap.

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%, so all 11 parameters are already documented, establishing a baseline of 3. The description only adds the location/company relationship and does not explain the nested 'properties' object or the boolean billing/contact flags beyond what the schema already says.

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?

States a specific verb and resource ('Add a new member (person) to a location'), and clarifies the optional company attachment. It implicitly distinguishes itself from officernd_update_member and officernd_get_member via 'add a new', though it never names them, so sibling differentiation is left to inference.

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?

There is no explicit when-to-use or when-not-to-use guidance and no named alternative. The only contextual hint is the passing 'optionally attached to a company', which implies a mode of use but does not tell the agent when to prefer this tool over update_member or how to handle the prerequisites.

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