Get an entity

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

readOnlyHint already covers the safety profile, and the description goes beyond it by disclosing the returned field set and explicitly scoping out per-channel account details. No mention of behavior when the ID is unknown (error vs empty), which is the remaining gap for a single-record lookup.

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 operation and return shape, then usage, then the alternative. No filler and nothing repeated from the schema or annotations.

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?

A one-parameter read tool with annotations present and no output schema — the description compensates by enumerating the returned fields and carving out the get_analytics boundary. Nothing needed to invoke it 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?

The single parameter is fully documented in the schema (uuid format and pattern), so the baseline is 3. The description adds real value by telling the agent where a valid entity ID can be sourced from, which the schema cannot express.

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?

Specific verb+resource ('Get one tracked entity by ID') followed by an enumeration of exactly what comes back: name, category, description, organization, and the four website slots. An agent can immediately tell this is a single-record fetch, distinct from the list-oriented find_entities sibling.

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?

Gives concrete entry points for the ID — search_mentions results, saved-search groups, channel-presence analytics — and explicitly routes per-channel account data to get_analytics with the channel-presence metric. It stops short of saying what to do when you only have a name and no ID (i.e., use find_entities first), which is the one obvious routing decision left unaddressed.

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