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

No annotations provided, so description carries full burden. It discloses that salt/digest stay hidden pre-reveal, which is a key behavioral trait. This helps the agent know what data is not returned, but could mention other behaviors like idempotency or error states.

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 very short (12 words) and front-loaded, but it omits important information like the action verb. It is concise but at the cost of clarity.

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?

Although there is an output schema (not shown in the input), the description does not mention what the tool returns or error scenarios. For a single-parameter read operation, it's minimally adequate but could be more complete.

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?

Parameter commitment_id is required but the description adds no meaning beyond the schema. With 0% schema description coverage, the description should explain the parameter's role or format, but it only says 'Current record for a commitment'.

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 says 'Current record for a commitment' which implies retrieval but lacks an explicit verb like 'get' or 'retrieve'. It distinguishes from siblings by mentioning 'pre-reveal' state, but the purpose is not immediately clear.

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 siblings such as list_commitments, commit, or reveal. The context signals show sibling tools, but the description provides no differentiation or usage hints.

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