get_invoice

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

No annotations are provided, so the description must carry the full burden of behavioral disclosure. However, it only states the basic purpose and does not disclose whether the tool is read-only, requires authentication, or what happens when the invoice is not found. The minimal description is insufficient for a tool with no annotations.

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 a single concise sentence, which is front-loaded and easy to parse. However, it is overly minimal, sacrificing completeness for brevity. A slightly longer description with additional context could improve it without losing conciseness.

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?

Given the lack of an output schema, the description should at least hint at what data is returned (e.g., full invoice object). The optional workspace_id parameter is unexplained. Compared to siblings with more detailed descriptions, this tool feels underspecified, even for a simple retrieval operation.

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 0% description coverage, meaning the description does not explain any parameters. While the schema provides names and types, the description adds no additional meaning beyond 'by id'. For example, it does not clarify the role of workspace_id (e.g., whether it disambiguates across workspaces).

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 explicitly states the verb 'get' and the resource 'invoice', specifying that it retrieves a single invoice by its ID. This clearly distinguishes it from siblings like list_invoices (which returns multiple invoices) and get_invoice_payments (which retrieves payments for an invoice).

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 provides no guidance on when to use this tool versus alternatives such as list_invoices or get_invoice_payments. It does not mention any prerequisites, restrictions, or context for using the optional workspace_id parameter.

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