get_business_summary

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

No annotations are provided, so the description carries the full burden. It indicates a read-only operation via 'Get' and lists the returned metrics, but does not disclose data freshness, response format, or any prerequisites. Given the simplicity of the tool, this is adequate but lacks richer behavioral context.

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, clearly structured sentence. It leads with the action and resource, then lists the metrics in a scannable format, making it both concise and front-loaded with no wasted words.

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 tool's low complexity (no parameters, no output schema), the description sufficiently covers the main purpose and included metrics. It could be slightly more explicit about the expected response structure or how the metrics are calculated, but for a simple summary getter, it is nearly complete.

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?

There are zero parameters, so the baseline is 4. The description adds value by specifying which metrics are included in the summary, which is beyond the empty input schema and helps set expectations for the return value.

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's function: 'Get business summary metrics' and lists specific metrics (total users, active users, paid users, pending payments, new users in the last 7 days). This is a specific verb+resource+scope, and it distinguishes from siblings get_new_users and get_pending_payments by being the aggregate summary tool.

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?

The description provides clear context by enumerating the metrics included, implying that this is the comprehensive summary tool while the siblings focus on individual metrics. However, it does not explicitly state when to choose this over the siblings (e.g., 'if you need all metrics, use this; for just one metric, use the specific tool'), so it stops short of explicit exclusions.

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