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

With no annotations, the description carries the full behavioral burden. It discloses that this is a GET endpoint, returns fixed JSON, and requires an explicit company, but says nothing about pagination, rate limits, or output behavior beyond the existence of an output schema.

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 short and front-loaded with the endpoint and key requirement. A few phrases such as 'Fixed JSON' and 'Flat query fields' are slightly cryptic, but there is no unnecessary text.

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 simple two-parameter list tool with an output schema, the description covers the required company and points to another tool for filters. It is adequate but leaves the opaque query object under-specified, which is a meaningful gap for an agent trying to build a filtered request.

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 0%, so the description must explain the parameters. It notes that company_name is required and that query fields are flat and discoverable via describe_nextesy_operation, but it does not describe the query object’s structure or any specific filter fields.

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 endpoint and HTTP method, making clear this is a read/list operation for credit notes. It does not explicitly distinguish this tool from siblings such as get_credit_note, but the resource and action are understandable.

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?

It states that an explicit company is required and directs filter discovery to describe_nextesy_operation, which gives some operational context. However, it does not state when to use this instead of get_credit_note or other sibling list/get tools.

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