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

Annotations are sparse (only destructiveHint=true and a title), so the description usefully adds 'WRITE', the required OAuth scope, and the backing endpoint. It does not disclose what the call returns (the new member's _id) despite there being no output schema, nor any failure/duplicate-handling behavior, leaving real behavioral gaps.

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 short sentences, front-loaded with the 'WRITE' marker and scope requirement before the resource description. Every clause carries information; no filler or repetition of the schema.

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 creation tool with a nested custom-properties object and no output schema, the description is adequate on the write/scope side but silent on the return payload and on the meaning of the surprising destructiveHint=true annotation. An agent can call it, but cannot anticipate the response.

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%, with all 11 parameters including the nested properties object documented in the schema itself, so the baseline is 3. The description only restates the location/company relationship already evident from the schema, adding no new syntactic or format detail.

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, optionally attached to a company.' An agent knows exactly what is created and the two key attachment dimensions. It stops short of naming its closest sibling (officernd_update_member) for contrast, so it lands at 4 rather than 5.

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?

Provides the prerequisite scope ('flex.community.members.create') and states that company attachment is optional, which is usable context. However, there is no guidance on when to prefer this over officernd_update_member or officernd_list_members, and no exclusions — usage is implied rather than specified.

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