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

Annotations already declare readOnly, idempotent, non-destructive, closed-world behavior, so the safety profile is covered. The description still adds value beyond them by disclosing response content: both the plan ceilings and the current consumption, plus the note that reporting follows Fetch Hive's own counting boundaries. It does not describe the response shape, but with no output schema this is only a minor omission given the field enumeration.

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, no filler, with the payoff clause about diagnosing refusals placed last for emphasis. The parenthetical list is long but each item carries information; the phrase 'with what is used where Fetch Hive counts it' is slightly tangled and could be phrased more cleanly.

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 parameterless read tool with full annotation coverage, the definition supplies the necessary scope, the fields returned, and the primary use case. The one remaining gap is that without an output schema the agent gets no sense of response structure or key names, only a prose enumeration.

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 takes zero parameters, so the baseline is 4 and there is no parameter semantics to compensate for. The description adds no argument concerns because none exist, which is appropriate.

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 the resource precisely and enumerates the concrete limits returned (steps per workflow, loop size, concurrent runs, workspaces, team members, API requests, storage, MCP gateways), which is far more informative than the bare name. It does not name or contrast with the adjacent get_usage sibling, so an agent must infer the boundary between plan limits and usage reporting, which is why it falls short of 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?

Gives a concrete triggering scenario: use it to explain why an operation was refused rather than retrying blindly. That is actionable guidance for the agent's decision loop. It offers no explicit when-not-use clause or named alternative (e.g., directing usage-only questions to get_usage), so it stays at 4 rather than 5.

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