get_proof_status

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

No annotations are provided, so the description carries the full burden. It mentions 'fetches', implying a read operation, but offers no details on side effects, permissions, idempotency, or error behavior. It does not disclose whether the operation is safe or what it might affect. The presence of an output schema partially mitigates return-format expectations but not behavioral traits.

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, efficient sentence with no redundant wording. It front-loads the action and resource. However, it is so minimal that it misses critical context; nevertheless, its structure is concise and free of filler.

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 one-parameter tool with an output schema, the description is still incomplete. It lacks any explanation of the parameter, does not characterize the expected output semantically, and provides no usage context. The agent is left without essential information to invoke the tool correctly.

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%, so the description must explain the parameter. It fails to mention deal_id, its purpose, format, or how it relates to the cryptographic manifest and TON transaction status. An agent cannot infer what value to supply without external knowledge.

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 it fetches cryptographic manifest and TON transaction status, using a specific verb and resource. It does not explicitly distinguish from siblings, though the operations are inherently different (seal, verify, get public key vs. status). Thus it meets the 'specific verb+resource' but falls short of explicit sibling differentiation.

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 provided on when to use this tool versus alternatives like seal_content or verify_content. There is no mention of prerequisites, intended context, or conditions for use. The description only states the act, leaving usage entirely to inference.

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