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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered; the description adds that this is a broad read-only aggregate spanning counts, billing/plan, month-scoped usage, and integrations. It does not disclose cost, response size, or whether the aggregation is expensive across many integrations, which with annotations in place is a modest gap.

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 with no filler, front-loading the resource ('How an organization stands') before the field list. The parenthetical enumerations are long but each item earns its place by telling the agent what data comes back.

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?

With no output schema, the description carries the burden of describing return content, and it does so explicitly across all three data groups. It could be complete at 5 by noting that the data is a point-in-time snapshot and whether it spans all integrations.

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?

Schema coverage is 100% and the schema description already explains the org identifier, accepted forms (accountId/website/name), and the omitted-default behavior. The description adds nothing about the parameter, so baseline 3 is correct.

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 enumerates exactly what the tool aggregates — source/draft/published/approved/rejected counts, plan and monthly usage, and integration states — so an agent can tell it is an org-level status snapshot. It lacks an explicit verb and never names the overlapping siblings (seovyn_plan, seovyn_integrations), which keeps it from 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 guidance on when to call this versus seovyn_plan or seovyn_integrations, even though those siblings surface a subset of the same data. The only conditional hint is the optional-org fallback, which is usage context for a parameter, not for tool selection.

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