run-custom-report

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It only says 'execute' and 'get results', but does not mention whether the operation is read-only, whether it can be long-running, how format affects output, or any error conditions. The lack of behavioral context beyond the basic action leaves significant gaps.

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, direct sentence with no fluff or repetition. It is front-loaded with the action and resource, making it quick to parse. There is no wasted wording.

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 simple two-parameter tool with no output schema, the description is adequate but minimal. It confirms that the tool returns results, but does not hint at result structure, pagination, or whether the format parameter is required. Since the schema fully covers parameters, some context is missing but not critical.

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 already describes both parameters with 100% coverage, so the baseline is 3. The description adds no additional meaning about reportId or format, relying entirely on the schema to document parameter semantics.

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 the verb ('Execute'), the resource ('a saved custom report'), and the outcome ('get results'). It does not explicitly differentiate from the sibling run-adhoc-report, but the phrase 'saved custom report' implies a distinction from ad-hoc reports, making the core purpose understandable.

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?

There is no explicit guidance on when to use this tool versus alternatives like run-adhoc-report or list-custom-reports. The description only implies usage through 'saved custom report', but never states prerequisites, exclusions, or conditions for choosing this tool.

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