get_cross_site_statistics

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

The description mentions a 'settings' parameter, but the input schema has no properties, creating a contradiction. Without annotations, the description fails to disclose any behavioral traits such as idempotency, side effects, or required permissions.

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 short but includes unnecessary docstring formatting. The contradiction between description and schema suggests it was not carefully reviewed. It is not a model of conciseness due to the error.

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?

Despite having an output schema (not shown), the description lacks details about what the aggregate statistics contain or how they are computed. The parameter mismatch further reduces completeness.

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 includes a parameter 'settings: Application settings' that does not exist in the input schema. This is misleading and adds conflict rather than clarity. Schema coverage is 100% because no params, but description adds erroneous information.

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 states the tool gets aggregate statistics across multiple sites. It is specific about the verb 'get' and the resource 'cross-site statistics', but it does not differentiate from potentially similar sibling tools like 'list_all_sites_aggregated' or 'search_across_sites'.

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. There are many sibling tools with overlapping functionality, but the description provides no context for selection.

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