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

No annotations are provided, so the description must carry transparency. It adds key context by stating 'Runs live FeedOracle assessment,' indicating real-time execution. However, it does not disclose return format, performance implications, side effects, or error conditions, leaving gaps for an agent.

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 two sentences, front-loads the primary action, and contains no redundant information. Every word contributes to understanding 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?

Given the tool's simplicity (one optional parameter, no output schema), the description covers the core function and the live-assessment aspect. It is distinct from siblings, though it lacks output details or clarification of 'FeedOracle.' This is sufficient for a basic assessment tool but not fully comprehensive.

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 one optional entity_id with a minimal description ('Entity ID (optional)'). The tool description adds no further meaning about the parameter, such as how to find or format entity_id. With 100% schema coverage, baseline is 3, and the description does not elevate 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 states a specific action: 'Assess ALL tokens for an entity in one call.' This clearly distinguishes it from the sibling tool assess_token, which likely handles a single token. The verb 'assess' and resource 'entity's tokens' are explicit.

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 phrase 'ALL tokens' implies a batch use case, contrasting with single-token assessment. It doesn't explicitly name alternatives but the 'ALL vs token' distinction provides clear context for when to use this tool. No exclusionary guidance is given, but for a simple tool this is adequate.

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