call_endpoint

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

Without annotations, the description discloses important behaviors: validation against a catalog, required authorization for mutations, and automatic backups. This provides good transparency about safety and constraints.

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 concise with four sentences, each conveying necessary information: purpose, validation, mutation behavior, and usage tip. No wasted words.

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?

The description covers validation and mutation authorization but omits response format and error handling. Given the tool's complexity and lack of output schema, more details on response and optional parameters would improve completeness.

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 main description mentions endpoint_name and required path parameters but does not elaborate on other parameters like body, files, query, file_field, or authorization fields. Given 0% schema description coverage, the description should compensate but falls short.

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 tool calls an Invoice Ninja API endpoint and returns its response. This clearly distinguishes it from sibling tools that list or describe endpoints.

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 advises using describe_endpoint first to learn parameters and specifies authorization requirements for mutating endpoints. However, it does not explicitly state when to avoid using the tool or when to use list_endpoints instead.

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