analytics_reports_get_instance

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

With no annotations, the description carries the full burden, and it discloses nothing beyond the 'GET' verb (which weakly implies a read). It does not say whether the lookup is scoped, what happens on a missing id, whether the response is cached, or which auth/app scopes are needed.

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?

Very short, but the single sentence is pure redundancy: the route appears twice in parentheses with no added information. Brevity here comes from omission rather than from efficient front-loading.

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?

There is no output schema and no annotations, so the description is the only place an agent could learn what this call returns and when to make it. It provides neither, leaving a bare REST route for a resource that is otherwise ambiguous among many analytics-related siblings.

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?

Schema description coverage is 100% and both parameters (id and fields_analyticsReports) are documented in the schema with enum values for fields. The description adds no meaning beyond the schema, so the baseline 3 applies.

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 is just the HTTP route repeated twice: 'GET /v1/analyticsReports/{id}'. It restates the tool name and path but never says what an analytics report is or what retrieving one returns. An agent learns only that some resource with that id exists.

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 when-to-use, when-not-to-use, or alternatives are given. Sibling tools like analytics_report_instances_get_instance and analytics_reports_instances_get_to_many_relationship sit alongside it, and nothing in the definition helps an agent choose between them.

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