get_profile

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

With no annotations, the description carries the full behavioral disclosure burden. 'Retrieve' implies a read-only operation, and 'stored, user-confirmed' adds a qualifier about which profiles are returned, but the description does not disclose what happens when no profile exists, whether any side effects occur, or what response is expected beyond what the output schema provides.

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 a single sentence with no filler. It front-loads the action, resource, and scoping qualifiers efficiently, making it easy for an agent to parse the core purpose quickly.

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?

The presence of an output schema means return values do not need to be explained. For a simple read-only getter with fully documented schema parameters, this description is reasonably complete, though it could have noted the scope parameter or provided guidance on sibling tools.

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 description coverage is 100%, so all parameters are already documented with defaults and meanings. The description adds a minor semantic link by naming host and workspace as selectors, but it does not provide meaningful information 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 states a clear verb ('Retrieve') and a specific resource ('stored, user-confirmed Agent Config profile'), scoped by host and workspace. It is distinct from siblings like get_setup_status or inspect_host because it targets the Agent Config profile, though it does not explicitly name those alternatives.

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 gives no guidance on when to use get_profile versus siblings like get_setup_status, inspect_host, or save_profile. There are no exclusions, prerequisites, or conditions that would help an agent choose this tool over alternatives; usage must be inferred solely from the verb.

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