get_control

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

Describes return format (not wrapped in array), 404 behavior, and enrichment from live CO set. No annotations provided, so description covers key behavioral traits adequately.

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?

Extremely concise, two short sentences front-loading purpose and critical details. No wasted words.

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?

With output schema present, description adequately covers return format and error case. Missing explicit parameter details but acceptable given schema. Remains clear for a simple getter.

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 75% with server_version lacking description. Description adds no parameter-specific information beyond what schema provides, missing opportunity to explain server_version or other parameters.

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?

Clearly states verb 'Get' and resource 'single control', specifies enrichment (verified-status, orphaned flag) and distinguishes from siblings like get_controls (plural) and get_control_objective.

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 for retrieving a specific control, but lacks explicit when-to-use vs alternatives or exclusions. Does not mention when not to use or how it differs from get_controls.

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