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

No annotations are provided, so the description must carry the behavioral burden. It explicitly discloses the output components, including the 30-day chart series, and the verb 'Get' plus 'summary' signals a read-only aggregation. It omits operational specifics like the exact definition of 'this period,' but for a parameterless summary call this is strong coverage.

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?

Two concise sentences with no filler. The main KPI summary is front-loaded, and the 30-day series is added as a brief, clearly separated clause. Every word earns its place.

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?

For a parameterless dashboard-summary tool, this is nearly complete: it lists every KPI group and the charting series, so an agent knows what it will get. The phrase 'this period' is somewhat underspecified and there is no output schema, but the description is adequate for correct invocation and high-level interpretation.

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 tool has zero parameters, so the schema provides no semantic burden and the baseline is 4. The description adds useful context about the scope of the summary ('this period') even though no parameters exist to modify it.

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?

Names a specific verb ('Get') and resource ('top-of-app KPI summary') and enumerates the contained metrics: total contacts, open deals with value, won deals with value, messages sent/received, and a 30-day series. This clearly distinguishes it from the many list/create/update siblings, none of which occupy the dashboard-summary role.

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 implies this is the tool to call when you need a dashboard-level KPI overview, but it does not explicitly state when not to use it or name alternatives for more granular data (e.g., campaigns_analytics or calls_list). There is clear context but no exclusionary guidance.

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