rn_styles

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

No annotations are provided, so the description carries the burden. It discloses useful behavior: styles are merged across the component chain, and StyleSheet.create styles surface as registeredStyleId. However, it does not address error handling, side effects, or the meaning of bundleId, leaving gaps in transparency.

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 with a front-loaded first sentence. The second sentence adds a technical detail about registeredStyleId, though the metaphor 'computed-styles panel React Native never had' is non-essential and could be trimmed without losing meaning.

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?

Without an output schema, the description partially explains expected results (resolved styles/props, registeredStyleId) but omits details about output structure, error behavior, and the optional bundleId. It is adequate for a simple inspection tool but leaves room for improvement.

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 coverage is 50%; testID is described but bundleId has no description in either the schema or the tool description. The description focuses on testID but does not explain bundleId's role or how it affects the resolution, failing to compensate for the low coverage.

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 resolves style and props for a given testID, with a specific verb ('Resolved') and resource. It distinguishes itself as a computed-styles tool among siblings, though it doesn't explicitly contrast with alternatives. The metaphor partially obscures but doesn't mislead.

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 implies usage for inspecting computed styles for a single testID, but provides no explicit guidance on when to use it over sibling tools like rn_component_tree or rn_eval. There are no exclusions or alternative references.

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