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

Goes well beyond the readOnly/idempotent annotations: cursor discipline ('follow every non-null nextCursor with unchanged filters and restart after edits'), page sizing defaults, the 'live inventory, not a snapshot of concurrent edits' caveat, and the meaning of trackedSince. These are real operational traits an agent needs before calling.

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?

Purpose is front-loaded and no clause is obviously wasted, but the content is delivered as one long semicolon-chained run-on that mixes pagination, identity semantics, and sibling routing. It is information-dense rather than cleanly structured, which slightly taxes parsing.

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 an output schema present, return-value explanation is unnecessary, and the description covers pagination loop behavior, filter semantics, scoping caveats, and successor tools. Nothing needed to invoke this live-inventory operation correctly is missing.

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 high (83%), which sets a baseline of 3, but the description adds genuine meaning: 'Omit tracked for all entries; true/false filters before pagination,' and the entityId-vs-competitorId distinction ('entityId is the stable identity; id is the saved roster row for recovery through competitorId'). This resolves ambiguity the schema alone leaves open for these lookalike UUIDs.

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 verb and resource ('Read the complete saved competitor roster for a Site, or tracked entities for a Topic') with clear scope qualifiers ('including entries with tracking switched off and incomplete identity setup'). An agent can distinguish this saved-roster tool from the discovery-oriented siblings without opening a schema.

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 routes mutations elsewhere: 'Use update_competitor to edit/re-enable, remove_competitor to remove membership, or update_topic to select a focal entity.' It also explains the empty-page outcome for a missing entry. It never states when to prefer this over the sibling list_discovered_competitors, so it falls short of full when/when-not coverage.

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