Group overview

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

Annotations already declare readOnlyHint=true, idempotentHint=true and destructiveHint=false, so the safety profile is covered and the description need not repeat it. What the description does add is the concrete return content — costs, margins, compliance traffic-light, pending-review counts, crop breakdown — which is genuinely valuable because no output schema exists. It remains silent on pagination, aggregation time window, and permission scoping, keeping it short of a 5.

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?

A single dense sentence that front-loads the resource ('Consolidated panel of a group') before the field list. Every clause carries content, though the field enumeration is list-heavy and could be tightened slightly.

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 one-parameter, read-only aggregation tool whose annotations fully cover the safety profile, the description supplies the missing return-shape detail that an absent output schema would otherwise leave blank. What is missing is the relationship to the other dashboard/list tools and any scoping or time-window caveats.

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 is a single parameter, group_id, and schema description coverage is 100% with the schema already pointing to list_groups as the source. The description implies the group scoping ('panel of a group') but adds no format, sourcing, or error detail beyond the schema, so the baseline 3 applies.

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 names a specific resource (a group) and precisely enumerates what the panel consolidates: per-farm entries, cost, income, margin, treated hectares, compliance status, pending reviews, crop breakdown, plus totals. An agent can tell this is a composite read/reporting tool. It does not, however, distinguish itself from sibling dashboards such as finance_dashboard or budget_variance, so it falls short of a 5.

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 when-to-use guidance, no statement of when this panel is preferable to finance_dashboard, budget_variance, advisor_pending or list_groups, and no exclusions or prerequisites. The agent must infer usage entirely from the tool name and the returned-field list.

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