GetStoreReportByCategory

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

With no annotations provided, the description carries full burden but discloses no behavioral traits (e.g., read-only, authentication needs, rate limits, side effects). The minimal description fails to inform the agent about tool behavior.

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 description is too short to be useful. While concise, it sacrifices clarity and completeness, omitting essential details. A good description is both concise and informative.

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?

Given the complexity (nested object input, many sibling tools, no output schema), the description is severely inadequate. The agent cannot reliably determine input structure or tool purpose.

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 single 'body' parameter has only a generic description 'Request body'. The description adds no meaning beyond the schema; the agent gains no insight into required structure or fields within the body.

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 'Get the report by category' identifies the action (get report) and dimension (category), but it is vague about what report and lacks distinction from sibling tools like GetStoreReportByChannel or GetStoreReportByDay. A more specific description would clarify the report type and scope.

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 tool versus alternatives. The description does not mention any prerequisites, context, or conditions, leaving the agent without direction on appropriate use cases.

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