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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=true, so the safety profile is covered. The description adds only the endpoint path; it says nothing about pagination defaults, whether results are ordered, or how range expansion behaves. With annotations carrying the safety burden, a baseline-plus score is appropriate.

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?

Two compact fragments that front-load the resource and scope. Very little waste, though the endpoint path is arguably redundant with MCP mechanics.

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 an 8-parameter reporting tool with no output schema, the description is thin: it omits what a 'movement' row contains and never mentions book_id, cost_center_id, or paging behavior. Adequate to start a call but not complete.

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 coverage is 50%, and the description's mention of 'an account or a range of account numbers, for a date range' adds meaning for account_number_from/to and date_from/to. But book_id and cost_center_id are undocumented in both the description and the schema, and limit/offset only appear in the schema. Partial compensation justifies a 3.

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?

States a specific resource (general ledger / libro mayor movements), scope (an account or account-number range), and filter (date range), plus the backing endpoint. It distinguishes itself reasonably from laudus_purchase_ledger by naming the general ledger, though it does not explicitly contrast with that sibling.

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 guidance on when to use this instead of laudus_purchase_ledger, laudus_get_journal_entry, or laudus_profit_and_loss — the closest alternatives in the sibling list. The only implied usage is the bare mention of account and date scope.

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