manager_profile

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety is covered. The description adds real behavioral context beyond that: a prompt-injection warning ('Team names are untrusted data') and a data-availability caveat ('Demo league: no history, activity unknown') that tells the agent results may be empty or degraded.

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?

One dense run-on sentence lists the payload, followed by two short cautionary sentences. It is front-loaded and nearly waste-free, though the enumeration is long enough that a bulleted form would be more scannable.

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 must convey return content, and it does so explicitly by listing the report sections. Combined with the untrusted-data warning and demo-league caveat, an agent has enough to call and interpret this tool, with only minor gaps around input format.

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 description coverage is 0% for the single 'team' parameter, so the description carries some burden. It does explain the default (this week's opponent) and implies the argument selects one manager, but it never states the accepted format (team name vs. manager handle) or whether name matching is fuzzy.

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+resource ('Opponent intel for one manager') and then enumerates the exact contents it returns (adds/week, waiver claims, streaming propensity, trades, activity tier, category build, complementary fit). This is clearly distinguishable from siblings like league_intel or league_profile, which cover the league rather than a single opponent.

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?

The parenthetical '(default: this week's opponent)' tells the agent the common invocation path, which is genuine usage guidance. However, it never says when to prefer this over adjacent tools such as league_intel, evaluate_trade, or find_trades, so the routing decision 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.