ARGENTUM

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

With no annotations provided, the description carries the full burden of behavioral disclosure. While 'Check' implies a read-only operation, it doesn't explicitly confirm safety, idempotency, or what occurs if the entity_id doesn't exist. It does disclose the three data categories returned (karma, actions, attestations).

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 extremely concise with no redundant text. The two-sentence structure efficiently separates the tool's purpose from the single parameter's semantics. However, embedding the parameter description directly in the main text block is slightly less structured than ideal.

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 presence of an output schema, the description appropriately avoids detailing return values. However, it fails to define what constitutes an 'entity' in this system or explain the relationship between karma, actions, and attestations, leaving contextual gaps for a tool dealing with reputation/verification concepts.

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?

The schema has 0% description coverage (entity_id lacks a description field). The text compensates by stating 'entity_id: the entity to look up', which adds basic semantic meaning beyond the schema's title and type, though it lacks format specifications, examples, or validation rules.

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 states specific actions ('Check') and resources ('karma', 'verified actions', 'attestations given'), clearly identifying what data is retrieved. However, it doesn't explicitly differentiate from sibling 'get_action_detail' which might also retrieve action information.

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 no guidance on when to use this tool versus alternatives like 'get_action_detail' or 'get_leaderboard', nor does it mention prerequisites such as requiring a valid entity_id format.

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