adb_profile_save

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

With no annotations, the description carries full burden for behavioral disclosure. It states 'save' and 'persist', but lacks details on overwriting behavior, error handling, permissions, or side effects. This is insufficient for an unannotated write operation.

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 sentences, each earning its place. The first sentence states the purpose; the second provides usage guidance. No fluff, well-structured, and easily digestible.

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 simple input schema (two string params) and no output schema or annotations, the description adequately covers the essential context: what the tool does, when to use it (after detect or manual), and the input nature. It could mention overwrite behavior, but overall it is nearly complete for this complexity level.

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 100% with descriptions for both parameters. The description adds context by mentioning that the profile can come from adb_profile_detect output or be manually composed with custom quirks and notes, which is not fully captured in the schema. This adds value beyond the schema.

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 'Save a device profile to the profiles library', specifying the verb 'save' and the resource 'device profile'. It distinguishes from sibling tools by mentioning adb_profile_detect and manual creation, making the purpose unambiguous.

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 explicitly says to use after adb_profile_detect or for manual profile creation, providing clear context on when to use the tool. However, it does not explicitly state when not to use it or mention alternative tools like adb_profile_list or adb_profile_delete, which would strengthen the guideline.

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