Show Instruction

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

Annotations already provide readOnlyHint=true and idempotentHint=true, indicating a safe read operation. The description adds the endpoint path and mentions it returns a JSON object, but does not disclose additional behavioral traits like pagination behavior or rate limits beyond what the schema implies.

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 three sentences long, efficiently stating purpose, usage, return type, required parameters, and API reference. It is front-loaded with the main action, but minor redundancy (mentioning 'Daily Log records' twice) prevents a perfect score.

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?

For a simple read operation with good annotations and complete parameter schema, the description provides the endpoint and clarifies the return format. It sufficiently covers what an agent needs to use the tool, though a brief note on the resource relationship (Instruction vs Daily Log) would enhance clarity.

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 100% with each parameter having a clear description. The description merely repeats the required parameters without adding new meaning; thus, it meets the baseline but does not exceed it.

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 the tool's purpose: 'Return detailed information on the specified Instruction' and 'fetch the full details of a specific Daily Log records by its identifier.' It uses a specific verb and resource, distinguishing it from sibling tools like show_accident_logs or show_call_logs.

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 description implies usage by stating 'Use this to fetch the full details' and lists required parameters, but does not provide explicit when-to-use or when-not-to-use guidance, nor does it mention alternatives among the many sibling show tools.

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