get_reporting_template

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

With no annotations provided, the description carries the full burden of disclosure. It describes the operation as retrieving a structure, which implies a safe read operation, but does not mention permissions, rate limits, or any potential side effects. It is minimally transparent but not misleading.

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 that is front-loaded with the key information (verb and resource) and provides enough detail without any waste. It earns its place.

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?

Given the simple single-parameter input and no output schema, the description is fairly complete. It explains what the tool returns (full structure including sections, metrics, etc.), which is sufficient for an agent to understand its purpose. Minor gaps: no mention of possible errors or return format, but adequate for a straightforward get operation.

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 100% coverage with a single parameter 'template_id' described as 'The reporting template ID'. The description adds context that the tool returns the full structure, which indirectly confirms the parameter's purpose, but does not add meaning beyond the schema. Baseline score 3 is appropriate.

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 'Get' and the resource 'reporting template', and specifies what is included: sections, metrics, dimensions, and visualizations. This distinguishes it from the sibling 'list_reporting_templates' which lists templates rather than retrieving one full structure.

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 implies that this tool is used when you need the detailed structure of a specific template, but it does not provide explicit guidance on when to use it versus alternatives like 'build_performance_report' or when not to use it. There are no exclusions or alternative suggestions.

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