Deeplink to Invoice

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

Annotations already mark the tool as readOnly, non-destructive, idempotent, and not open-world. The description adds minimal behavioral context (view/edit), but does not explain if the link expires or requires authentication. No contradiction with 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, front-loaded sentence of 12 words that conveys the core purpose without any fluff or 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 one-parameter tool without an output schema, the description is minimally adequate. However, it would benefit from clarifying the link format or response structure, as the agent only knows it returns 'a direct link' but not in what form (e.g., plain string, JSON).

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 schema has 100% coverage for the single parameter 'id' with a detailed format description. The tool description does not add new meaning beyond stating the resource type. 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?

The description clearly states the action ('Get'), the resource ('a direct link to view/edit an invoice'), and it effectively distinguishes this tool from its siblings such as lexware_get_invoice which returns invoice data, not a link.

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 implies the tool is used when a link to view/edit an invoice is needed, but it lacks explicit guidance on when to use it versus alternatives (e.g., lexware_get_invoice for data). It also does not mention prerequisites like the invoice existing.

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