homer_get_call_flow

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

No annotations provided. Description only says 'retrieve', implying read-only behavior but does not explicitly state that it has no side effects, requires specific permissions, or is rate-limited. It fails to disclose behavioral traits beyond the basic retrieval action.

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?

Description is brief with a clear header and parameter list. It is front-loaded with the core purpose. Could be slightly more efficient by removing the 'Parameters' header redundancy, but overall concise.

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 an output schema present, the description need not cover return values. However, it lacks context on when to use this tool relative to other Homer tools, and does not mention any limitations or constraints. It is minimally viable but not enriched.

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?

Input schema has 0% coverage (no descriptions in schema). The description compensates by explaining the single parameter: 'The SIP Call-ID to fetch the flow for.' This adds meaningful context beyond the schema's minimal label.

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?

Description clearly states 'Retrieve the SIP call-flow (ladder diagram) for a call from Homer,' specifying the verb 'retrieve' and the resource 'SIP call-flow'. It distinguishes from sibling tools like homer_get_call_transaction by mentioning 'ladder diagram', though not explicitly contrasting them.

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?

No guidance on when to use this tool versus alternatives like homer_get_call_transaction or homer_search_calls. There is no mention of prerequisites, required state, or scenarios where this tool is preferred.

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