get_report_queries_suid_permissions

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

With no annotations, the description carries the behavioral disclosure burden. It does disclose the operation as a read-only GET and mentions pagination/filters, but it leaves auth requirements, required header contents, and error behavior unspecified; 'any required request headers' is vague.

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 sentences with no filler. The endpoint is front-loaded, and the parameter guidance is compact and actionable.

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 description plus output schema covers the basic invocation shape, but with no annotations and a 0%-coverage schema, it omits required header specifics, body semantics, and pagination details. For a generic REST tool this is not fully complete.

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 0%, so the description is the only source of parameter meaning. It usefully maps route IDs to path_params and filters/pagination to query, but it does not explain the body parameter, define what route IDs are valid, or specify filter/pagination formats.

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?

States a specific action ('Retrieve suid permissions') and the exact endpoint (`GET /report_queries/suid_permissions`), making the tool's purpose clear. It does not explicitly differentiate from siblings, but the resource and verb are unambiguous.

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 parameter-placement guidance (route IDs in path_params, filters/pagination in query, headers in headers) but does not say when to use this tool versus the many similar report-query siblings, nor does it mention exclusions or alternatives.

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