get_sales_summary

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

No annotations are present, so the description carries full burden. It indicates a read operation but offers no details on side effects, idempotency, auth requirements, or rate limits. The 'introspection stub' remark may confuse whether the tool is functional.

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 very short, but the structure is fragmented: starting with a bracket-enclosed tag, then a phrase, then environment notes. It is concise but not well-organized.

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 7 optional parameters, no required ones, and no output schema, the description lacks information about return format, pagination, filtering behavior, or use cases. It is insufficient for a tool of this complexity.

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?

All 7 parameters have descriptions in the schema (100% coverage), so the baseline is 3. The description does not add additional meaning or context beyond 'Daily final/priced revenue and estimates'.

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 includes a tag '[Inventory / read]' and states 'Daily final/priced revenue and estimates', which provides a clear verb (get) and resource (revenue and estimates). However, it does not distinguish this tool from similar siblings like get_sales_and_traffic or get_todays_sales.

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 is provided on when to use this tool versus alternatives. The mention of 'Hosted endpoint only; this local stdio server is an introspection stub' is about environment, not usage context.

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