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

The description clearly discloses key behavioral traits beyond the annotations: it does not create holdings, does not appear in the investor pipeline, and warns that duplicating a name results in duplicate register entries. The annotations only provide openWorldHint=false and destructiveHint=false, so the description carries the main behavioral burden and does so effectively, though it doesn't address side-effects or error cases.

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 longer than average but every sentence contributes substantive guidance. It's front-loaded with the core scoping statement, then gives exclusions and a reliable alternative. There is minor redundancy between the two 'do not call the following' sentences, but overall it is well-structured and efficient for the complex decision it supports.

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 a cap table tool with a deeply nested single parameter, the description is remarkably complete. It not only explains what the tool does but also the business context (pipeline, holding, register) and the correct operational sequence. The output schema exists to explain return values, so the lack of return-value detail is not a gap. An agent has enough context to call this tool correctly.

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?

Since the schema description coverage is 0%, the description must compensate for the single nested parameter. It does name the identity subset (name, type, email, metadata), which adds meaning, but it does not explain the full set of fields such as title, userId, address, companyId, etc., nor the enum values. The 'identity only' framing is useful, but the description leaves some parameter-level detail unstated.

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 opens with a specific action and scope: 'Adds a stakeholder IDENTITY ONLY (name, type, email, metadata).' It explicitly distinguishes this from holding/security creation, and the caveat about not appearing in the pipeline further disambiguates it from sibling tools like RecordCapTableInvestment. The agent can immediately understand what this resource is and is not.

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?

The description gives explicit when-to-use and when-not-to-use guidance: 'Use this tool only for a party who is genuinely meant to have no holding at all.' It names the alternative tool (RecordCapTableInvestment) and instructs on the correct call order, including how to pass a previously returned stakeholder_id. This is textbook usage routing.

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