meroshare_get_current_issues

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

No annotations are provided, so the description must fully disclose behavior. It only states what is listed (open issues) but omits safety traits (read-only, idempotent), authentication needs, or rate-limiting concerns. For a listing tool, additional transparency is expected.

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?

A single, focused sentence with no wasted words. It is front-loaded with the core action. It could be slightly improved by including pagination context, but remains efficiently sized.

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 simple two-parameter list tool, the description is minimally adequate. It identifies the resource but does not mention pagination behavior or return format. Without an output schema, some return details would improve completeness.

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 parameters have clear descriptions and defaults. The tool description adds no extra meaning beyond the schema; baseline 3 is appropriate.

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?

Description clearly states the verb 'list' and the resource 'currently open IPO, FPO, and Rights share issues', making the tool's purpose immediately obvious. It naturally distinguishes from sibling tools like meroshare_apply_ipo (which applies) and meroshare_get_bank_details (bank info).

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 implies this is a read-only listing tool but provides no explicit guidance on when to use it versus alternatives. Sibling tool names are given in context, but no when-not or exclusion criteria are stated.

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