inspector_get_details_subtree

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It mentions connecting to a Flutter debug port, which hints at network/remote operation, but doesn't describe critical behaviors such as error handling, response format, whether it's read-only or has side effects, performance implications, or authentication needs. For a tool with no annotations, this leaves significant gaps in understanding how it behaves beyond basic functionality.

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 concise and well-structured in two sentences: the first states the core purpose, and the second adds connection details. There's no unnecessary fluff, and it's front-loaded with the main functionality. However, it could be slightly more efficient by integrating the port information more seamlessly, but overall it's effective and wastes no words.

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?

Given the complexity of a debugging tool with no annotations and no output schema, the description is incomplete. It doesn't explain what the 'details subtree' includes, the response format, error conditions, or how it integrates with sibling tools. For a tool that likely returns structured widget data, more context is needed to guide effective use, especially without annotations to cover behavioral aspects.

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 input schema has 100% description coverage, with clear documentation for both parameters: 'objectId' as the widget ID and 'port' as an optional custom port. The description adds minimal value beyond the schema, only reiterating the default port (8181) without providing additional context like format examples or constraints. Given the high schema coverage, the baseline score of 3 is appropriate as the schema does most of the work.

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 clearly states the tool's purpose: 'Get the details subtree for a widget. This provides detailed information about the widget and its descendants.' It specifies the verb ('Get'), resource ('details subtree for a widget'), and scope ('widget and its descendants'). However, it doesn't explicitly differentiate from sibling tools like 'inspector_get_children_details_subtree' or 'inspector_get_root_widget_summary_tree', which appear related but have different scopes or detail levels.

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 some usage context by mentioning the default Flutter debug port (8181) and the option to specify a custom port, which implies this tool is used in debugging scenarios. However, it doesn't explicitly state when to use this tool versus alternatives like 'inspector_get_children_details_subtree' or 'inspector_get_root_widget_summary_tree', nor does it outline prerequisites or exclusions. The guidance is implied rather than explicit.

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