Organization brand overview

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

Annotations already establish read-only, idempotent, non-destructive, closed-world behavior, so the safety profile is covered. The description adds genuine behavioral context: that this is a current-state snapshot with no date filtering, that it aggregates across all active projects, and that it includes an organization-level rollup row. It does not mention auth, rate limits, or pagination, but for a read-only snapshot call those are minor.

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?

Three sentences, front-loaded with the resource and its grain ('one row per brand'), followed by the constraint and the alternative. Dense but every clause carries information; the column list is long but useful, and the closing example question is slightly redundant.

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 compensates by enumerating the returned fields and the ranking plus org-level aggregate, and it states the temporal semantics. What is missing is any guidance on sourcing organizationId and the absence of pagination/volume expectations for a cross-project board.

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?

Only one parameter (organizationId) and schema description coverage is 0%, so nothing in the structured data explains it. The description hints that project ids come from this call but never clarifies what organizationId is or where to obtain it. Baseline 3 given the single flat parameter, with a real gap left unaddressed.

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?

States a specific resource (organization-level brand rank-health board) with verb-like scoping ('latest-snapshot'), and enumerates the exact columns returned (share of voice, mention rate, avg position, positivity, tracked-query count) plus the org-level aggregate. It is clearly distinguished from the per-project siblings it names.

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?

Explicitly declares a negative constraint ('takes NO date window') and routes to the alternative for date-ranged comparison (get_project_rank_tracking_stats per project id). It also gives a concrete triggering question the tool answers, which pins down when to select it.

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