create_service_outward

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

With no annotations, the description carries the full burden and does disclose a significant behavioral trait: on success the agent must output the exact returned text verbatim, without converting to tables or adding markdown summaries. This is genuinely useful beyond what any schema could convey. It omits permission requirements and failure behavior, but the post-success output contract is substantial.

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?

Two sentences, with purpose front-loaded in the first. The CRITICAL instruction is somewhat verbose ('without converting it into tables or adding extra markdown summaries, so the user can easily copy and send...') but the redundancy reinforces a behavior that is easy to get wrong. Overall efficient with no 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?

For a create tool with six parameters, no annotations, no output schema, and 33% schema coverage, this description is incomplete. It implies the tool returns a copyable notification message but never specifies required inputs, alternatives, side effects, or failure handling. An agent would still need to inspect the schema and siblings to invoke it correctly.

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 only 33%, so the description must compensate for the six underspecified parameters, but it provides none. It does not clarify that company_id and service_lines are required, what sac_code or gst_rate mean within service_lines, or the format of date beyond the schema's YYYY-MM-DD hint. The phrase 'professional services, maintenance, etc.' vaguely hints at service_types but adds no concrete parameter guidance.

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 states a specific verb ('Create') and resource ('service billing invoice to clients for professional services, maintenance'). The phrase 'to clients' distinguishes it from the sibling create_service_inward, and 'service billing invoice' differentiates it from sales/purchase invoices. Purpose is immediately clear.

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 only guidance is 'CREATE ONLY,' which is a scope constraint rather than usage direction. The description never states when to choose this tool over create_service_inward, create_sales_invoice, or other create siblings, nor does it mention prerequisites such as needing a party_id or existing company_id.

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