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

Annotations already declare readOnlyHint, destructiveHint=false and openWorldHint=false, but the description still adds real behavioral context: the ledger is append-only, reads current server state without manufacturing facts, is idempotent, and falls outside the confirmation boundary. That said, the confirmation-boundary sentence lumps in unrelated operations (reversible save, plan refresh) that do not apply to a read tool, diluting the signal.

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 functional sentences at the front are tight and well-ordered (what it reads, what is included, treasury-share caveat). The trailing confirmation-boundary clause sprawls into a list of unrelated operations, most of which have nothing to do with a read, padding the definition without adding value.

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 no output schema, the description usefully sketches what the ledger returns (opening balances, issuances, repurchases, treasury vs. shareholder votes). But the prerequisite and confirmation sections are boilerplate referrals rather than real conditions, and parameter behavior is entirely unaddressed, leaving the definition only partially complete for a tool in a large sibling set.

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% across two parameters, and the description never mentions companyId or the nested _corply_context object, so it does not compensate for the gap. The agent gets no explanation of UUID formatting expectations or the role of the context receipt from the prose.

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 gives a specific verb and resource ('Read the append-only stock ledger') and enumerates the contents (opening balance snapshots, completed issuances, repurchases), which is more than a restatement of the title. It does not, however, distinguish itself from a close sibling like get_cap_table, leaving the agent to infer why both exist.

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?

Usage is implied by the resource name, but there is no explicit when-to-use guidance and no named alternative such as get_cap_table. The stated prerequisite ('authenticated active company access plus every prerequisite stated above') is circular and references text that does not exist in this definition, so it provides no actionable gating condition.

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