get_report_schedule

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

There are no annotations, so the description must carry the burden of behavioral disclosure. It only says 'Get a specific report schedule' and provides no information about read-only behavior, return format, error conditions, permissions, or any side effects. The get operation is inherently read-only, but the description adds no context beyond that.

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 clear sentence with no unnecessary words or repetition. It is appropriately sized for a simple getter tool and front-loads the key action and resource.

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 is simple with two well-documented parameters, but there is no output schema and no annotations. The description does not mention what is returned (e.g., the full schedule object) or any potential errors. It is minimally complete for a getter but lacks the extra context that would make it fully self-sufficient.

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 input schema has 100% description coverage for both parameters (schedule_id and report_config_id), so the baseline is 3. The description itself adds no additional meaning beyond the schema; it does not explain how the parameters relate or provide extra context.

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 'Get a specific report schedule' uses a clear verb ('get') and resource ('report schedule') and explicitly indicates it retrieves a single item ('specific'). This distinguishes it from siblings like list_report_schedules which list multiple schedules, and create/update/delete variations.

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 about when to use this tool versus alternatives. It does not mention that it requires both parameters or contrast with list_report_schedules or get_report_schedule_generated. Usage context is entirely implied by the verb, with no explicit when-to-use or when-not-to-use.

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