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

Annotations already declare readOnlyHint=true and destructiveHint=false, but the description adds real context: idempotency ('safe to repeat'), canonicality (reads current server state, does not manufacture facts), the confirmation boundary, and the pass-through-at-cost nature of the state charge. The enumerated funding-status values, including legacy_review requiring Ops reconciliation, further clarify behavior.

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 returned fields are front-loaded usefully, but the back half is boilerplate ('Prerequisite', 'Canonicality', 'Idempotency', 'Confirmation boundary') with one sentence that defers to non-existent 'prerequisites stated above.' The funding-status parenthetical is dense but earns its place.

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 correctly covers the return payload in detail, but it leaves the input side unexplained (two required UUIDs and a nested context object) for an agent that must supply all three. Prerequisite wording that points to absent text further reduces 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 0% across 3 parameters, so the description carries the burden and does not meet it. companyId, caseId, and the nested _corply_context object are never mentioned; only an oblique 'approved governed charter amendment' hints at caseId.

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?

It names a specific verb+resource (read a charter filing quote) and enumerates the returned components: Delaware state charge, Corply filing fee, total, and Corply Pay funding status. It is clearly distinguishable from mutation siblings like checkout_charter_filing, though it never names that alternative 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?

Usage is only implied: it applies to 'an approved governed charter amendment' with 'authenticated active company access.' The 'plus every prerequisite stated above' clause is a self-reference to text that isn't in this description, so it gives no actionable when-to-use guidance and does not contrast with checkout_charter_filing.

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