get_compliance_status

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

With no annotations, the description carries the full burden and does so effectively. It discloses prerequisite scope requirements, upstream behavior (no auth, live computation from soc2-tracker.json), and that every call is governed by policy and sealed with a ProofLink receipt. This adds meaningful behavioral context beyond a simple 'get scores' statement.

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 concise and front-loaded, with the core purpose and deliverables in the first sentence, followed by behavioral and prerequisite details in the second. It is dense but avoids filler, and every sentence contributes meaningful information.

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 zero-parameter interface and absence of an output schema, the description covers the necessary contextual elements: what the tool returns (specific scores, evidence status, gap analysis, source tracker file), prerequisites (scope), and behavioral notes (live computation, receipt). It is complete enough for correct invocation, though the output format is only listed as components rather than a detailed structure.

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?

The tool has zero parameters, and the schema coverage is trivially 100%. Per the rubric, a zero-parameter tool gets a baseline of 4, and there is no parameter-specific information needed beyond the schema. The description does not mention parameters, which is appropriate here.

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 identifies the action ('Get') and the resource ('live compliance scores for the iTechSmart platform'), and specifies the exact frameworks (NIST CSF, HIPAA, SOC 2). It is specific and informative, though it does not explicitly distinguish itself from sibling tools like compliance.audit_summary or get_platform_briefing.

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 purpose implicitly suggests when to use the tool (when compliance scores are needed), but there is no explicit guidance on when not to use it or how it compares to alternative tools. The description provides clear context but lacks exclusionary or alternative-referencing information.

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