get_activity_stats

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

Since no annotations are provided, the description carries the full burden of behavioral disclosure. It only lists the metrics (CA, orders, quotes) and temporal grouping, but does not state whether the operation is read-only, what permissions are required, the response format, or how missing periods are handled.

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 a single concise sentence with no redundant wording. It directly conveys the core function and is easy to scan.

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?

The tool has no output schema and no annotations, so the description must explain return structure and edge cases. It does not describe whether the result is a list or summary, units for CA, or handling of empty periods. This is inadequate for an analytics tool and leaves many gaps.

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 schema has 2 parameters; month has a description (1-12, optional) but year has none. The description's 'par mois/année' hints at temporal grouping but does not clarify whether year is required, valid ranges, or the effect of omitted parameters. This adds minimal value beyond the schema, which already covers month but not year.

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 clearly identifies the tool's purpose: providing activity statistics (CA, orders, quotes) aggregated by month/year. This distinguishes it from siblings like get_mailing_stats or get_financial_summary. However, it is a noun phrase without an explicit verb (e.g., 'retrieves'), which slightly reduces clarity.

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 sibling list contains many analytics tools (e.g., get_financial_summary, get_vat_report), and the description does not mention preferred contexts, exclusions, or contrast with similar functions.

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