get_connector_stats

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

With no annotations provided, the description alone must convey behavioral traits. The phrase 'Get overall statistics' implies a read operation but does not state authorization needs, rate limits, aggregation behavior, or whether the 'period' parameter affects the aggregation. This leaves significant behavioral ambiguity.

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, front-loaded sentence with no wasted words. It efficiently states the action, though it could have included more context without harming conciseness.

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?

While the schema is simple (one optional parameter) and there is an output schema, the description fails to define what 'Feather Connector' refers to or to distinguish this from sibling stats tools. Given the existence of get_crm_stats and get_growth_metrics, the description is incomplete for an agent to know when to invoke this tool.

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 input schema already fully documents the single 'period' parameter with a description and enum values, achieving 100% schema coverage. The tool description adds no additional meaning beyond the schema, so the baseline score of 3 is appropriate.

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 uses a specific verb ('Get') and a clear resource ('Feather Connector statistics'), making the tool's basic action apparent. However, it does not differentiate this from sibling tools like get_crm_stats or get_growth_metrics, both of which are also statistics tools, leaving ambiguity about what 'Connector' specifically covers.

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 guidance on when to use this tool versus alternatives such as get_crm_stats or get_growth_metrics. The description does not provide context for selecting this tool over the sibling statistics tools, nor does it mention any exclusions.

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