get_issue_stat

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

Annotations declare readOnlyHint=true and destructiveHint=false, but the description adds no extra behavioral context. 'Python SDK parity' is an obscure reference that does not explain pagination, return format, auth needs, or rate limits, offering no value beyond the structured annotations.

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 extremely brief but not effectively concise—it is under-specified. A single phrase with no structured breakdown of purpose, usage, or behavior does not serve the agent, despite being short.

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 tool has 2 parameters, no output schema, and many siblings, but the description provides no substantive information. It fails to explain what 'issue_stat' refers to, what the response contains, or how it differs from similar tools, making it completely inadequate for safe and correct invocation.

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 descriptions cover 100% of parameters: 'ids' is described as package IDs from send_package, and 'dry_run' as showing the request without sending to API. The description itself adds no parameter information, but the schema does the heavy lifting, meeting the baseline for high coverage.

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 only gives the HTTP endpoint and 'Python SDK parity' without stating what the tool actually does. It implies retrieving issue statistics from the name, but no verb or resource semantics are clarified, and it fails to distinguish from sibling tools like get_statistics or api_get_v1_get_smtp_issue_stat.

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?

There is no guidance on when to use this tool versus alternatives. With a large sibling list including get_statistics, get_package_status, and api_get_v1_get_smtp_issue_stat, the absence of any context or exclusions leaves the agent without direction.

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