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

With no annotations, the description carries the full burden. It adds some behavioral context—that access is 'Free' and that weekend calls are 'locked Sunday 19:45 ET, graded in public'—but does not disclose return format, whether the operation is read-only (implied but unstated), or other operational traits like rate limits.

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 a single, front-loaded sentence with no wasted words. The colon-and-list structure efficiently groups the content categories, though the cryptic phrasing ('where each Chainlink stock reference wakes') slightly reduces immediate clarity.

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 zero-parameter tool with no output schema and no annotations, the description should more clearly state what the tool returns and in what form. It lists the data categories but never says 'returns' or describes the response structure, leaving a gap in completeness.

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 tool has zero parameters, so the baseline is 4. Schema coverage is 100% but irrelevant here; the description need not compensate for missing parameter documentation.

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 identifies a specific resource (PARALLAX's Night Desk agent) and lists its content categories (weekend calls, track record, weeknight notes), distinguishing it from siblings like parallax_gap or parallax_pricing. However, it lacks an action verb (e.g., 'returns' or 'fetches'), leaving the tool's operation vague rather than stating a clear verb+resource.

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?

No explicit guidance is given for when to use this tool versus its six siblings, nor are any prerequisites or exclusions stated. Usage is only implied by the content description—if you want Night Desk info, use this—but there is no direct instruction.

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