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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so safety is fully covered elsewhere. The description adds nothing about response shape, pagination, or scoping rules, only a pointer to describe_operation for schemas.

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?

Very short, but the sole content sentence is duplicated word-for-word, so a third of the text is pure waste. The operation ID and describe_operation pointer are the only non-redundant content.

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?

A tool with an undocumented required param, a free-form nested query object, and no output schema needs more than a restated path. An agent cannot tell what values 'module' accepts or what the response contains.

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% and the description never explains the required 'module' path parameter or the free-form 'query' object. With two parameters and no schema documentation, the description should compensate but supplies nothing.

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 repeats the HTTP path twice and adds nothing about what a 'module field' is or what set of records is returned. It restates the title verbatim, making it close to tautology, though the path does at least indicate a GET on a module-scoped resource.

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?

No indication of when to call this versus the near-identical sibling get_accounting_integration_module_field_4d5cadee1442775f9d9fd558 or describe_operation/execute_read. The only guidance is a pointer that describe_operation holds native schemas, which is not a usage condition.

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