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

The description adds significant behavioral context beyond the annotations: it explains access restrictions (free businesses), required prerequisite calls (check_business_tool_access), and UI steps (show warnings). Annotations already indicate readOnlyHint=true and no destructiveness, so the description enriches but does not contradict. However, it does not detail what happens if called without prerequisites (e.g., error behavior), which keeps it from a 5.

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 description is four sentences, front-loading the main purpose and then providing procedural steps. It is efficient but could be more structured (e.g., bullet points for prerequisites). No wasted words, but the density of instructions in later sentences makes it slightly dense.

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 two parameters and no output schema, the description covers the essential usage context: permissions, business tier restrictions, prerequisite calls, and UI actions. It lacks details on the return value (invoice config contents) but given no output schema, this is acceptable. The description is sufficiently complete for an agent to invoke safely.

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?

The input schema has no descriptions for the two parameters (communityId, transactionId). The description does not add any meaning to these parameters; it only mentions 'for a community transaction' generically. With 0% schema coverage, the description should compensate but fails to clarify the role or format of the parameters. This is a significant gap.

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 clearly states the tool gets 'invoice configuration for a community transaction.' It specifies the resource and action, and distinguishes itself from sibling get_* tools by referencing the unique context of transaction invoice configuration. Additional context about prerequisites (permissions, business tier) further refines purpose.

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 explicitly instructs when to use the tool: before offering the action or requesting inputs, check business permissions; free businesses cannot use; call check_business_tool_access; show grace-period warning and verified resubscribe link; never proceed when access is blocked. This provides clear when-to-use, when-not-to-use, and prerequisite steps.

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