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

No annotations are provided, so the description carries the full disclosure burden, and it discloses very little. 'Fixed JSON' hints at response format and 'GET' implies a read, but there is no mention of permissions/authentication, pagination or response shape, side effects, or rate limits. For a tool with zero annotation coverage, this is a substantial gap.

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?

Three short clauses, no filler, and the mandatory-company constraint is stated up front. The telegraphic style ('Fixed JSON GET ...') is terse to the point of being cryptic but earns its space.

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?

An output schema exists, so return values need not be explained. But with no annotations and an opaque free-form query object, the description leaves the agent dependent on an extra describe_nextesy_operation round-trip to call this correctly. Adequate as a signpost, incomplete as a self-contained definition.

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%, meaning neither parameter is documented structurally, so the description must compensate. It does add that company_name is mandatory and that query is a 'flat query fields' object, plus it redirects to describe_nextesy_operation for valid filter keys – useful, but the actual query keys and their formats remain undisclosed.

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 operation through its HTTP path (GET /api/v1/document/preferences), from which an agent can infer it retrieves document preferences. However, it never states the purpose in plain language or a verb like 'retrieve', and gives no differentiation from nearby siblings such as get_document, get_document_numbering, or get_banking_preferences. The intent is inferable but not stated.

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?

'Explicit company required' gives one concrete precondition, and the pointer to describe_nextesy_operation tells the agent where to look for filter options. There is no statement of when this tool should be preferred over siblings like get_document or get_document_numbering, so usage is only implied.

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