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

Annotations already declare readOnlyHint=true and destructiveHint=false, so safety is covered. The description adds no behavioral context beyond that: it does not say what happens if no IP registration exists (null, empty, or error), what the return payload contains, or whether the lookup is chain-backed or cached.

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?

A single front-loaded sentence with no filler; the target resource and lookup key appear immediately. It is efficient, though extremely terse, leaving no room for the routing or edge-case context an agent would benefit from.

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 annotated read with a complete one-parameter schema and no output schema, the description covers the basics but is silent on the not-found case and on how the result relates to sibling IP tools. Adequate but with a clear gap around error/empty behavior.

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 100% for the single parameter, so the schema already documents 'capabilityId' fully. The description only restates the key relationship ('by its capability ID') without adding format, source, or constraints — baseline 3 is appropriate.

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 a specific verb ('Get') and resource (the Story Protocol IP registration for a capability) and specifies the key used ('by its capability ID'). This is unambiguous on its own, though it does not explicitly distinguish itself from nearby siblings like get_registration, get_ip_lineage, or register_capability_ip.

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_registration or get_ip_lineage, nor any stated preconditions (e.g., the capability must already have a registration). The agent must infer usage entirely from the name and purpose.

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