get_manifest_component

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

No annotations provided, so description carries burden. Describes 'retrieve' as read operation but gives no detail on behavior (e.g., error handling, whether data is parsed, performance). Does not disclose what happens on invalid component_type or manifest missing. Minimal behavioral context.

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?

Two concise sentences, first states core action and filter, second adds supported types. No extraneous text. Front-loaded with key information.

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 30+ sibling tools and no annotations, description covers basics but misses crucial context: prerequisites (e.g., manifest already loaded), return behavior on missing components, and any side effects. Output schema exists but description standalone lacks completeness for safe invocation.

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 has 0% description coverage, so description adds value by listing examples for component_type (activity, provider, etc.) and explaining only_exported as a filter. Clarifies that component_type refers to standard Android components, improving schema understanding. Could specify whether component_type is restricted to those four.

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 the verb 'retrieve' and resource 'component data from AndroidManifest.xml'. It distinguishes itself from siblings like 'get_android_manifest' by specifying it targets a single component type with optional export filtering. Lists supported component types (activity, provider, service, receiver) for exactness.

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?

Implied usage: use when you need a specific component's data with optional exported filter. However, no explicit when-to-use or when-not-to-use compared to alternatives like 'get_android_manifest'. No prerequisites mentioned. Lacks guidance on choosing between this and other get_* tools.

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