Solentic

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

Annotations already indicate this is a read-only, non-destructive, idempotent operation. The description adds valuable context beyond annotations: it specifies what gets verified (no private keys logged, Memo Program instruction presence, wallet generation behavior) and that it returns git commit hash and source code links. This provides important behavioral details about verification criteria.

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 efficiently structured in three sentences: purpose statement, output specification, and verification criteria. Every sentence adds value with zero redundant information, making it easy to parse and understand the tool's function.

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 verification tool with no parameters, rich annotations, and no output schema, the description provides good completeness. It explains what gets verified and what's returned, though it doesn't detail error conditions or format of returned links. Given the annotations cover safety aspects, this is reasonably 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?

With 0 parameters and 100% schema description coverage, the baseline would be 4. The description appropriately doesn't discuss parameters since none exist, and instead focuses on what the tool does and returns, which is correct for a parameterless tool.

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: 'Verify the code running on Blueprint servers' with specific outputs (git commit hash, direct links) and verification goals (check for private keys, Memo Program instruction, wallet generation behavior). It distinguishes from sibling tools like 'get_verification_links' by focusing on integrity verification rather than just link retrieval.

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 provides clear context for when to use this tool: to verify deployed code integrity on Blueprint servers. It doesn't explicitly state when NOT to use it or name alternatives, but the verification focus differentiates it from general performance or transaction tools in the sibling list.

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