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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint, so the safety profile is covered. The description adds output scope but no behavioral traits beyond that; it does not contradict the annotations. This is a standard, adequate level given rich annotations.

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?

Two sentences, with the core resource and scope front-loaded. The second sentence ('Identical to the paid page's timeline') is somewhat marginal for an agent but not distracting; overall it's concise and structured well.

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?

Without an output schema, the description gives a useful high-level outline of the returned data (dated and cited filings), but it does not specify structure, ordering, or filing types. It is adequate for a single-parameter read-only tool, but gaps remain.

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 the ticker parameter is already well documented (one ticker, no batch). The tool description adds nothing beyond the schema, so the 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?

The description clearly identifies the resource (share-issuance timeline for one ASX company) and the content (every issuance-relevant filing, dated and cited). It is specific and not a tautology, but it does not explicitly differentiate from sibling tools like get_raise_history, so it stops short of a 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?

The description implies when to use the tool (when you need a company's issuance timeline) and the schema adds a concrete constraint (one company per call, no batch form). However, there is no explicit guidance about alternatives or when not to use it, so it does not fully meet the 4-bar.

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