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 description adds substantial beyond-annotation context: secrets are addressed by name and never surfaced as values, spend caps are evaluated against what has been PAID rather than earned, and anti-fraud hold/maturity semantics. It omits error/empty-campaign behavior, so it falls short of 5.

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?

The key operation is correctly front-loaded in the first clause, but the rest is an oversized data-model essay covering schedules, rate cards, milestones, budgets, providers, moderation and anti-fraud that an agent does not need in order to select or invoke a single-parameter getter. Much of this belongs in the returned model's documentation, not the tool description, so it is over-specified rather than concise.

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?

For a one-parameter read with no output schema, the description compensates thoroughly by explaining what the field contains and, importantly, what it does NOT contain. It is complete enough for correct invocation; the only minor gap is any hint about behavior when no campaign is configured.

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?

There is a single parameter (title_id) with 100% schema description coverage, so the schema already carries the semantics. The description adds no syntax or format detail about title_id, so the baseline 3 for fully-covered schemas 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?

The opening states a specific verb+resource+scope: 'GET ONLY the CommunityMarketing field of TitlePublicConfigurationModel,' and it clarifies what Community Marketing is (creator reward program). It distinguishes itself from siblings by asserting that operational data (creators, submissions, accruals) lives in other collections, so an agent can tell it apart from save_community_marketing and the operational getters 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?

It clearly frames the read-only config-retrieval context and explicitly excludes related-but-separate data (creators, submissions, journal) and the funding source (Currency section). However, it never names an alternative tool (e.g., save_community_marketing for writes), so the routing guidance is implied rather than explicit, which keeps it out of the top band.

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