content_provider

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

With no annotations at all, the description carries the full load. It does disclose two genuinely useful behaviors: update/delete demand an explicit where clause, and where='1' means all rows (a destructive-footgun warning), plus that ROM/provider authorization still applies. However it says nothing about permission failures, whether calls are reversible, or concurrency, so the mutation risk profile remains only partially disclosed.

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 dense sentences with no filler, and the operation list is up front. The parenthetical about '1' meaning all rows interrupts the flow, and cramming two separate ideas (bindings, authorization caveat) into one sentence makes it slightly harder to parse.

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?

An output schema exists, so return values needn't be explained. Given zero annotations and eleven undocumented parameters, the description is missing detail an agent would want: the meaning of root, user_id, max_output_bytes, and whether permissions must be pre-granted.

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 0% across 11 parameters, so the description must compensate. It explains three of the most important parameters: action maps to the chosen CRUD verb, where is the selection filter, values carries the typed payload implicitly. It adds no meaning for uri, projection, sort, arg, method, root, user_id, max_output_bytes, so it falls short of full 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?

States a specific resource (Android ContentProvider) and enumerates the concrete operations (query/insert/update/delete/call/gettype) plus the key qualifier 'zero-UI' and 'typed bindings'. That distinguishes it from UI-driven siblings, though it never names which sibling (e.g. query_system_provider, sqlite_database) it competes with.

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?

Implies usage via 'zero-UI' (bypass the UI layer and hit the provider directly) and gives one hard precondition for update/delete. It does not say when to prefer this over query_system_provider, shared_preferences, or sqlite_database, so the agent must infer the choice from the URI scheme.

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