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

Annotations already declare readOnlyHint/destructiveHint=false, but the description adds non-obvious traits: canonicality ('reads current server state and does not manufacture company facts') and idempotency ('safe to repeat'), neither of which is in the annotations. The confirmation-boundary sentence is boilerplate policy text mixing in unrelated actions (reversible save, link preparation, plan refresh), which dilutes an otherwise useful disclosure.

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 opening clause is well front-loaded, but the listing of four labeled clauses (Prerequisite/Canonicality/Idempotency/Confirmation boundary) pads a simple read tool, and the confirmation-boundary sentence enumerates unrelated operations that do not apply here.

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 read-only tool with no output schema the description does identify the returned content (facts, source hash, certificate link), but it omits return shape detail and leaves the dangling 'prerequisites stated above' reference and undocumented parameters unresolved.

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 0% for two parameters, so the description carries the burden of explaining companyId and the nested _corply_context object. It says nothing about either, so an agent gets no help on what to pass or why the context object exists.

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?

Specific verb+resource: 'Read the latest accepted ... charter facts, source hash and certificate link' tells the agent exactly what is returned. It positions itself against propose_charter_amendment ('before proposing a name or authorized-share amendment'), though it never names the sibling explicitly.

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?

Gives a clear usage trigger ('before proposing a name or authorized-share amendment') and a prerequisite (authenticated active company access). However, the phrase 'plus every prerequisite stated above' refers to text that is not in this definition, leaving an unresolvable condition.

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