report_account_list

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

With no annotations supplied, the description carries the entire burden, and it discloses almost nothing behavioral: no statement that it is read-only, no permission requirements, no pagination or row-limit behavior, and no explanation of what a date range means for an account listing. Only the vague 'showing all accounts and their details' hints at the return shape.

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?

One front-loaded sentence with no filler, and the resource is identifiable immediately. The clause 'showing all accounts and their details' mildly restates the report name, but it is short enough to be acceptable.

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?

As a simple report tool with no output schema, the description is not required to explain return values. However, for a report whose filtering semantics (dates applied to an account list) are non-obvious and whose params object is open-ended, it leaves meaningful gaps an agent would want filled.

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?

The description mentions no parameters at all, leaving the nested date_macro/start_date/end_date semantics entirely to the schema. While those nested property descriptions are informative, the wrapper 'params' object has no description and declares additionalProperties: {}, so the description should have said which report-specific filter options 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?

Names a specific verb ('Run') and resource ('Account List Detail report') and states the content ('all accounts and their details'), so an agent can tell it produces an account listing rather than a single account lookup. It does not, however, distinguish itself from nearby siblings like search_accounts or report_customer_balance_detail.

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 guidance, no mention of prerequisites, and no named alternative such as search_accounts or get_account. The agent must infer from the name alone that this is for bulk/report-style account retrieval rather than a targeted lookup.

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