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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description adds valuable behavioral context: that shared secrets (SSV keys, report keys) are NOT stored here and only the TitleSecrets entry name is returned, which prevents an agent from expecting credential material in the response.

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 read-scope constraint is front-loaded in the first clause. The long enumeration of sub-features is verbose but largely earns its place by scoping what 'Advertising' means; the two-sentence structure is coherent, though the list is denser than strictly necessary.

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 read-only single-param tool with no output schema, the description does enough — it defines the field's domain and the secrets caveat. It stops short of describing the return shape or noting any auth/permission needs, which is a minor 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?

With a single parameter and 100% schema description coverage (title_id fully documented in the schema), the schema carries the parameter semantics. The description adds nothing about title_id, so 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 and resource ('GET ONLY the Advertising field of TitlePublicConfigurationModel') and enumerates exactly what that field contains. An agent can immediately tell this apart from save_advertising or get_title_data.

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 'GET ONLY' phrasing and contrast with the write-path sibling save_advertising imply this is the read-side tool, but there is no explicit statement of when to use it versus alternatives like get_title_data (which may or may not also expose advertising). Usage is implied rather than spelled out.

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