meroshare_apply_ipo

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

No annotations are provided, so the description carries full burden. The description mentions dry_run for preview but does not disclose post-submission behavior (e.g., confirmation, error handling, idempotency) or authentication requirements. This is insufficient for a complex mutation tool.

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 extremely concise with only two sentences, no wasted words. It front-loads the core purpose and immediately adds a key usage hint.

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?

Given 10 parameters, no output schema, no annotations, and sibling tools that provide prerequisites, the description fails to provide sufficient context. It does not explain the application workflow, expected return values, or error scenarios.

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?

Input schema has 100% coverage with detailed parameter descriptions. The tool description adds minimal value beyond mentioning dry_run. Baseline 3 is appropriate since schema already documents parameter semantics well.

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 clearly states the tool applies for an IPO/FPO/Rights issue, using specific verbs and resource types. It distinguishes from sibling tools like meroshare_get_current_issues which only retrieve data.

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 suggests using dry_run=true to preview, which provides basic usage guidance. However, it lacks explicit instructions on when to use this tool versus alternatives, such as ensuring prerequisite data (e.g., bank details, company share ID) are obtained first.

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