list_request_count

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description adds only the endpoint URL, which is not a behavioral trait. It does not disclose what the response contains (e.g., a single integer vs. an object) or any authentication/rate-limit considerations.

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, front-loaded with the purpose, and includes an HTTP endpoint. There is no wasted text, but the brevity means it omits potentially useful context, so it doesn't reach a 5.

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 no-parameter, read-only tool with an output schema and annotations, the description's 'Gets request counts' is minimally sufficient. However, it does not clarify whether this returns a total count or counts by status, nor does it help an agent choose between this and list_request. The sibling list provides some hints, but the description itself is not 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?

The tool has zero parameters and the input schema lists no properties, so the description has no need to add parameter-level meaning. The baseline of 4 applies because schema coverage is complete and no parameters exist to document.

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 'Gets request counts' states a specific verb and resource. It distinguishes from list_request (which returns full request objects) and list_issue_count (which counts issues). However, it is minimal and does not detail what 'request counts' means, so it is not a 5.

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 provides no guidance on when to use this tool versus alternatives like list_request or list_issue_count. It contains no when-to-use advice, exclusions, or conditions, leaving the agent to infer from sibling tool names.

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