List billing history (invoices)

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

With readOnlyHint/idempotentHint already declared, the description adds value by disclosing pagination and by spelling out the return shape (including the payable flag and the three link types), which matters because there is no output schema. It omits auth/permission requirements and what happens on an empty history, so it stops short of full 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?

Three compact segments, front-loaded with what it does and what comes back; nothing is buried. 'Read-only.' restates the readOnlyHint annotation, which is the only minor redundancy.

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, 3-optional-param list tool with no output schema, the description carries the return-shape burden well and pagination is covered by the schema. It is only slightly incomplete: no note on authorization requirements or empty-result behavior.

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 each parameter (page, per_page, payable_only) is documented in-schema, including the whole-history semantics of payable_only. The description's phrase 'whether payable' lightly corroborates the payable concept but adds no syntax or defaults beyond the schema, 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 precise verb+resource ('List your Crown Town Compost invoices') and enumerates exactly what each row contains (number, date, amount, status, payable flag, Stripe PDF/receipt/hosted page links). The resource name alone separates it from siblings like crowntown_list_service_history and crowntown_list_upcoming_services.

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 offers no when-to-use guidance: it never says to reach for this tool instead of crowntown_get_account or crowntown_get_dashboard, nor does it mention the payable_only narrowing path that would be the natural 'billing actions' use case. 'Paginated. Read-only.' is behavioral, not situational.

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