get_r_report_queries_problems_summary_asset_details

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

No annotations are provided, placing the full burden on the description. The description only says 'Retrieve records' and repeats the endpoint; it does not disclose authentication requirements, pagination defaults, rate limits, or any side effects (even though GET is likely read-only). The agent gets no behavioral insight beyond what the endpoint name implies.

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?

Two concise sentences with no filler. The endpoint is front-loaded and the parameter placement guidance follows directly. The structure is efficient and scannable.

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 tool with no annotationsressing and an empty schema, the description lacks essential context: no explanation of what 'problems_summary_asset_details' returns, no indication of whether route IDs are mandatory (schema says all optional but description says 'provide' them), and no relation to sibling tools. An agent would still have to guess about output shape and prerequisites.

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 0% coverage and all parameters are untyped empty objects, so the description must compensate. It does add a high-level mapping: path_params for route IDs, query for filters/pagination, headers for required headers. This is meaningful, but it doesn't name any specific parameters, formats, or required vs optional status. It is better than nothing but far from complete.

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 states the action ('Retrieve records') and identifies the exact endpoint, which is more than a tautology. However, it doesn't explain what 'problems_summary_asset_details' means semantically or how this resource differs from the many similar report query siblings. An agent would understand it calls that endpoint but not what domain value it provides.

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 gives explicit guidance on where to place inputs: route IDs in path_params, filters/pagination in query, and headers in headers. This is useful and directly actionable. However, it provides no when-to-use guidance versus alternatives, so an agent cannot decide between this and other report query tools based on the description alone.

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