crosswalk_to_iso27001

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

Discloses read-only, stateless, idempotent behavior, rate limits (free/pro tiers), and authentication requirements, providing full transparency beyond the absent annotations.

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?

Well-structured with sections (Args, Behavior, When to use), but some redundancy (e.g., 'Behavior' section repeats idempotency) could be trimmed for conciseness.

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?

Covers purpose, behavior, usage guidelines, and rate limits comprehensively; output schema exists, so return format is covered. All necessary context for safe and correct invocation is present.

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?

With 0% schema coverage, the description adds meaning for key parameters (soc2_series with examples, focus_principle with enum values), but does not describe api_key and gives minimal detail on caller and tier.

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 'Map SOC 2 controls to ISO 27001 Annex A controls' with specific verbs and resources, distinguishing it from sibling tools like control_gap_analysis by focusing on cross-mapping between two specific frameworks.

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?

Includes explicit 'When to use' and 'When NOT to use' sections, but lacks direct comparison with sibling tools or guidance on when to choose this tool over alternatives like control_gap_analysis.

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