ecount_call

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It fails to indicate whether the call is read-only or mutating, authentication requirements, rate limits, or side effects. The description only says 'calls the endpoint,' giving zero behavioral context.

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 short sentence, but it is under-specified rather than concise. It fails to convey essential context, so the sentence does not 'earn its place.' Similar to the 'Process' example, this is a lack of content, not effective 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?

For a generic OAPI/V2 caller with no annotations, the description is insufficient. It does not explain that behavior depends on the endpoint, potential side effects, or error handling. Although the schema covers parameters and an output schema exists, the description does not provide enough context for safe agent invocation.

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 100% description coverage for both parameters (endpoint and payload). The tool description itself adds no parameter information beyond what the schema provides. Since schema coverage is high, the baseline is 3, and there is no additional value from the description.

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 identifies the action ('calls') and resource ('ecount OAPI/V2 endpoint') but is vague about what the endpoint actually does. It does not differentiate this generic call tool from sibling tools like ecount_save_customer or ecount_save_invoice, which are specific operations. It is not a tautology, but it lacks specificity.

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 information about when to use this tool versus the sibling tools. It does not state that this is a low-level generic caller for arbitrary endpoints, nor does it mention any exclusions or alternatives. An agent has no guidance on tool selection.

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