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

Annotations already declare readOnlyHint, idempotentHint, non-destructive, and closed-world, so the safety profile is covered. The description adds nothing beyond that — no mention of pagination, filtering behavior, or what a 'chart' contains — so it contributes no behavioral value.

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 single substantive sentence is duplicated verbatim, which is pure waste, and the operation ID hash adds no meaning for an agent. What remains is short but consists of restated URL and internal metadata rather than useful front-loaded 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?

With no output schema, 0% parameter coverage, and nested objects, the description needs to explain parameters and return shape, but it only points to describe_operation. That pointer helps but leaves the definition well short of what an agent needs to call this correctly.

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 two nested parameters (query, params) are undocumented. The description compensates only by deferring to describe_operation, giving no syntax, format, or meaning for either parameter.

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 restates the raw HTTP endpoint ('GET /api/gl-accounts/charts') twice rather than stating in domain terms what the tool returns. An agent cannot distinguish it from siblings like get_gl_accounts, get_gl_accounts_types, or get_gl_accounts_assignments, since 'charts' is never explained.

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?

There is no when-to-use or when-not-to-use guidance. The only actionable pointer is that describe_operation provides native request schemas, which aids invocation but says nothing about selecting this tool over its many gl-accounts siblings.

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