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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so safety is covered; the closing sentence ('never changes the agent or its work') largely restates that. The real added value is the inventory of what the payload contains (tasks, runtime/budget, recent runs, messages, knowledge, source files, review clips, Editor projects, Spy signals), which is meaningful given no output schema.

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?

Front-loaded with the verb+resource, then the prerequisite, then the read-only guarantee. The long enumeration of returned data is dense but earns its place since there is no output schema; only the near-redundant restatement of the read-only hint is filler.

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 usefully characterizes the return payload and the id-resolution path, which is enough to call this read tool correctly. It could go one step further by distinguishing itself from get_influencer_agent, which is the main remaining gap.

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 already documents agentId as a UUID from list_content_agents. The description repeats the same provenance, adding no format or edge-case 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?

States a specific verb (fetch) and resource (content-team agent) plus scope (by id, with full read-only dashboard context). It also enumerates the returned surface areas and distinguishes itself from list_content_agents, so an agent can identify it without opening the 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 instructs 'Call list_content_agents first to resolve the id', which is concrete prerequisite guidance. It does not, however, address when to prefer this over the sibling get_influencer_agent, so the when-not case is left to inference.

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