reddit get reporting schema

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is well covered. The description adds a scope boundary around targeting, but it does not disclose other behavioral context such as whether the schema is static or dynamic, nor does it mention rate limits or auth requirements.

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 description is a single efficiently structured sentence that front-loads the tool's purpose and then adds a precise exclusion. Every clause carries useful information with no redundancy.

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?

The tool has an output schema, so the description need not explain return values, and annotations already cover safety traits. The description provides enough scope and sibling differentiation for an agent to call it correctly, though it could be slightly more explicit about how the reporting schema relates to reddit_get_insights.

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 tool takes zero parameters, so there are no parameter semantics to explain. The baseline for zero-parameter tools is 4, and the description does not need to compensate for missing parameter documentation.

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 description identifies the resource as a 'Reddit metric and dimension inventory,' making clear that the tool returns reporting schema metadata. It distinguishes the tool from reddit_get_targeting by stating that configured targeting is read elsewhere and should not be inferred from reporting, though it lacks an explicit verb like 'retrieve' or 'list.'

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 description explicitly names an alternative (reddit_get_targeting) for configured targeting and clarifies that such data is not available through this reporting schema. However, it does not explicitly state when to use this tool, such as when constructing reporting queries or interpreting available metrics, leaving that use case implied.

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