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

Annotations already declare readOnlyHint=true, idempotentHint=true, openWorldHint=false, so the safety profile is fully covered by structured data. The description adds no behavioral context such as scoping, filtering requirements, or pagination, so it contributes nothing beyond the annotations.

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 content is a duplicated URL string rather than front-loaded meaning; the repetition wastes the entire budget without conveying anything useful.

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 tool with a nested free-form query object, zero parameter documentation, and no output schema, the description supplies none of the context an agent needs to invoke it correctly, and it does not explain the relationship to the sibling module-field tool.

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 says nothing about the two parameters. The free-form 'query' object (additionalProperties: {}) is entirely undocumented, leaving the agent to guess what query keys are accepted.

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 only repeats the raw endpoint path 'GET /api/accounting-integration/module-fields' twice, which restates the title rather than explaining what a module field is or which module's fields are returned. An agent cannot distinguish this from the near-identical sibling get_accounting_integration_module_field_54b26c135c8bbb56776effa3.

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 when-to-use or when-not-to-use guidance is given, and no alternative is named. The only actionable pointer is that 'describe_operation provides native request schemas', which hints at a discovery workflow but says nothing about selecting this tool.

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