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

With no annotations, the description carries the full burden and does so well: it discloses pricing ($0.04/page up to 25 pages in USDC via x402), that the cost is quoted before payment, that failed reads are free, and that it performs arithmetic checks. These are exactly the behavioral traits an agent needs before invoking a paid tool.

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?

Front-loaded with the core purpose, then return values, then pricing. The enumeration of returned fields is long but each item is meaningful for an agent that cannot see an output schema. Slightly dense but free of filler.

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 steps in to describe return values in detail (gross this period, retainage, contract sum, balance to finish, payment due; change-order type/number/amount/date), and it also covers input limits and cost. Nothing essential to calling it correctly is missing.

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%, so all four parameters (gc, document, fileName, subcontractor) are already documented in the schema. The description adds the 3 MB/25-page limits and mentions GC/subcontractor context indirectly but adds no syntax beyond what the schema provides, so the baseline 3 applies.

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?

States a specific verb (reads) and resource (AIA G702/G703 pay applications, change orders, Procore/Textura versions) and the transformation (PDF into structured JSON). This is unmistakably distinct from the unrelated siblings 'about' and 'request_capability'.

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 scopes usage by naming exactly which document types are supported (G702, G703, Procore/Textura, change orders), which lets an agent decide fit. It does not state exclusions or point to an alternative, but the sibling tools are unrelated, so little routing guidance is needed.

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