get_r_report_queries_companies_by_application_suppressed

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

With no annotations, the description carries the full behavioral burden. It does imply a read-only GET operation, but it does not disclose authentication expectations, side-effect absence, pagination behavior, or anything about the response beyond the existing output schema.

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 short and front-loaded, with the endpoint and invocation guidance in two sentences. The phrase 'Retrieve records' is somewhat redundant with 'Calls GET', but the overall structure is efficient.

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 annotations and a large sibling set, the description is too thin. It lacks a plain-language explanation of what the suppressed companies-by-application report contains, what body is used for, and when to prefer this endpoint over the unsuppressed variant.

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 must compensate. It adds meaning to path_params (route IDs), query (filters and pagination), and headers (required request headers), but it completely ignores the body parameter. Partial compensation, not 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 identifies the operation as a GET that retrieves records from a specific endpoint, so the resource and verb are clear. However, it never explains what 'companies_by_application_suppressed' actually returns, and it does not distinguish itself from the very similar sibling get_r_report_queries_companies_by_application.

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 and pagination in query, headers'), but it provides no when-to-use context and no comparison to alternatives. An agent cannot tell when to select this tool over the many related report-query siblings.

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