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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It says only 'record or view' without explaining side effects, whether recording overwrites existing data, what 'view' returns, or any permissions needed. The dual-mode behavior is acknowledged but not detailed.

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, grammatically complete sentence with no redundancy, which is concise. However, for a tool with 8 parameters, this brevity borders on under-specification rather than effective conciseness. It does not structure information for the agent (e.g., by grouping parameters or outcomes).

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 complexity (8 parameters, no annotations, no output schema), the description is drastically incomplete. It does not explain parameter meanings, the distinction between recording and viewing, or expected outputs. An agent cannot reliably invoke this tool based on the provided information.

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 0%, and the description mentions none of the 8 parameters. The schema contains enums for 'result' and 'test_type', but without explanation of how they map to behavior, the agent cannot correctly select or fill parameters. The description fails entirely to compensate for the schema's lack of semantic context.

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 uses a clear verb ('record or view') and identifies the resource ('test execution evidence for a change'). This resource is distinct from sibling tools like approval_check and register_change, which focus on other aspects. However, the dual verb 'record or view' introduces ambiguity about whether the primary action is mutation, retrieval, or both.

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 is given about when to use this tool versus alternatives. The description does not mention prerequisites, exclusions, or relationships to sibling tools. An agent would have to infer usage from the name and context, which is insufficient for a tool in a complex change-management workflow.

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