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

No annotations are provided, so the description must carry the full burden of behavioral disclosure, but it does not. It does not state whether the operation is read-only, whether authentication is needed, or any error/rate-limit behavior. It only lists content items without any behavioral commitments.

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 short, but this is under-specification rather than effective conciseness. It is a fragment, not a sentence, and fails to include the essential verb and parameter guidance; the minimal text does not earn its place because it provides little actionable information.

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 one-parameter tool with no output schema and no annotations, the description is the only documentation. It lists some output topics but fails to explain the required parameter, the return format, or any usage caveats, making it severely incomplete for any agent to call 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?

The schema contains a single required parameter keyId with no description, and schema coverage is 0%. The description does not mention keyId at all, leaving the agent without any semantic information about what keyId represents or how to use 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 'Standing, tier, and what each karma entry was for.' is a noun phrase lacking a verb; it never explicitly states that the tool retrieves or returns this data. It hints at the resource (passport karma) but does not clearly define the operation, nor does it differentiate from siblings like get_passport or open_passport.

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?

There is no guidance on when to use this tool versus alternatives such as get_passport or open_passport. No conditions, exclusions, or preferred use cases are mentioned, leaving the agent without context for tool selection.

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