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

The description paints a purely read/diagnostic operation (returning verbs, costs, health, stats), yet the annotations declare readOnlyHint=false, implying the call may mutate state. That read/write mismatch would mislead an agent judging safety. Flagged as an annotation contradiction.

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?

It opens with a front-loaded hook ("What can I do, what does it cost, what's down?") then enumerates the returned contents efficiently. Dense but every clause carries information; no padding.

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?

With no output schema, the description usefully enumerates the return payload and notes env values are returned as booleans, never values (a valuable privacy detail). But the read/write ambiguity created by the annotations is unresolved, leaving the agent less certain than it should be about the operation's side effects.

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 100% (both handle and secret documented), so the schema does the baseline work. The description adds that the parameters are an owner gate ("Owner-gated: your handle+secret"), which clarifies why both exist without adding syntax, so the baseline 3 holds.

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 states a specific, distinctive capability: a single introspection call returning integration verbs with credit costs, live service health (hindsight/voicestudio/litellm), missing env keys, and per-verb latency/error stats. It is clearly distinguishable from siblings like get_tool_schema, discover_tools, identity, or memory_stats. It doesn't explicitly name those siblings, so it stops 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?

"One call" implies the intended usage (a consolidated status/capabilities query), and "Owner-gated: your handle+secret" gives the prerequisite. However, it never states when to prefer this over discover_tools or get_tool_schema, nor any exclusion. Usage is implied rather than instructed.

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