fetch_assessment_run_leaf_control_evidence

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

No annotations provided. Description discloses return structure and possible error, implying a read operation. Lacks deeper behavioral context like permissions, side effects, or rate limits.

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?

Concise with clear header and structured args/returns. Every sentence adds value, though the detailed return description could be slightly trimmed if output schema is sufficient.

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 tool's simplicity (one parameter, flat output), the description adequately covers purpose, input, and output. It does not mention empty list handling or prerequisites, but is sufficiently complete for a basic fetch tool.

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%, so description adds value by naming the parameter as 'Assessment run control id'. This adds meaning beyond the bare schema, but could be more specific about format or source.

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 'Get leaf control evidence for given assessment run control id', specifying verb, resource, and input. However, it does not distinguish from siblings like fetch_evidence_records or fetch_automated_controls_of_an_assessment.

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?

No guidance on when to use this tool versus alternatives, nor any context about prerequisites or conditions. The description only provides input and output details.

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