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

The description goes far beyond the readOnlyHint/openWorldHint annotations by detailing cost, rate limits, no persistence, privacy projection (stripped fields, pseudonymization), trace size cap with truncation flag, and that raw PCAP is not returned to agents. It also explains the dual behavior of using persisted diagnostics vs. parsing on the fly. This fully discloses behavioral traits.

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 long but front-loaded with a concise cost/read-only/rate-limit banner, then moves from core behavior to details and pairings. Every section serves a purpose for a complex tool; however, the length is substantial and some details (e.g., media-quality explanation) could be trimmed without losing essential guidance. Still well-organized.

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 output schema, the description thoroughly inventories what the agent can expect: trace text, AI analysis, metadata, rule-based diagnostics, media quality stats, truncation, raw-capture exclusion, and privacy projection. It also gives practical next-step tool pairings, making the response complete enough for an agent to decide and act correctly.

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 schema already provides a detailed description for the url parameter (full URL, path must be /share/<token>, not /api/share). The tool description adds useful semantic context about accepted URL forms ('any sipflow.dev subdomain') and what the tool does with the URL, but the parameter itself is already well-covered by the schema. Baseline is 3, and the added subdomain detail and context raise it to 4.

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 uses specific verbs ('load', 'fetch', 'hydrate') and clearly identifies the resource: a Sipflow share URL. It distinguishes the tool from siblings by stating its unique role: fetching shared SIP traces plus AI analysis in one round trip, and explicitly names sibling tools for different purposes (e.g., render_sip_ladder, review_sip_config).

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 explicit when-to-use guidance: 'Use this whenever a user pastes a /share/<token> URL.' It also frames alternatives and complementary tools ('Pair with: review_sip_config... minimize_sip_trace... troubleshoot_response_code'), clarifying the tool's role relative to siblings. It does not need an explicit when-not because the positive trigger is unambiguous.

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