camelot_cap_table_manager

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

Annotations already indicate idempotentHint=true, destructiveHint=false, and readOnlyHint=false, so the safety profile is covered. The description adds 'Local browser processing,' which provides some behavioral context about where computation happens, but it does not disclose what the tool actually does with the shareholder data, whether it produces a document or table, or what side effects occur despite idempotency being true. No annotation contradiction is present.

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 short and front-loaded with the purpose phrase, but it contains filler: the trailing 'Canonical URL' is not useful for tool invocation, and the double period suggests sloppiness. The 'Local browser processing' sentence adds some value but could be more substantive.

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 an output schema present and the input schema well-documented, the baseline information is adequate. However, the description fails to clarify the core action ('Manage' is ambiguous), does not reconcile the mention of vesting schedules with the available shareholders-only input, and does not explain what kind of output the agent should expect beyond the schema's existence.

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%, and each property (name, shares, shareClass) has a clear description, so the schema carries the parameter semantics. The description adds no meaningful detail about the shareholders parameter beyond the schema, and it even mentions vesting schedules that are not represented in the input schema.

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 identifies the resource (cap table) and themes (ownership percentages, share classes, vesting schedules), but the verb 'Manage' is broad and does not specify whether the tool creates, edits, validates, or generates a cap table. It does not distinguish this tool from siblings like camelot_equity_dilution_calculator, and it promises vesting schedule management despite the input schema only covering shareholders.

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 given for when to use this tool versus alternatives such as camelot_equity_dilution_calculator or camelot_business_plan_generator. The phrase 'Local browser processing' hints at where processing occurs, but it does not explain the intended use case, prerequisites, or when a better-suited sibling exists.

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