direct_get_time_targeting

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

With no annotations, the description carries the full burden. It labels the operation as 'READ', which implies non-mutating behavior, but says nothing about return format, error conditions, or whether the schedule is for a specific date range. The word 'READ' is largely redundant with the 'get' in the tool name.

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 one concise line with no filler. It is front-loaded with the action, though the 'READ:' prefix could be seen as slightly redundant with the tool name. Overall, it is appropriately sized for a simple getter.

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 no output schema and no annotations, so the description should explain what the return value looks like. It only says 'READ: campaign TimeTargeting schedule', leaving out details such as the structure of the schedule or potential empty results. This is inadequate for full contextual completeness.

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 schema has 0% description coverage for the single required parameter, campaign_id. The description mentions 'campaign' but does not explain the parameter's meaning or expected values beyond what the schema already shows, failing to compensate for the coverage gap.

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 clearly states a specific action ('READ') on a specific resource ('campaign TimeTargeting schedule'). It distinguishes itself from sibling tools like direct_set_time_targeting by indicating the read operation.

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?

No guidance is given on when to use this tool versus alternatives. For example, it does not mention that direct_set_time_targeting should be used to modify the schedule, nor any prerequisites.

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