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

With no annotations, the description carries the full burden of behavioral disclosure. It describes the card's contents but does not state that this is a read-only operation, whether it can return empty results, or any data freshness or availability behavior. The 'get' prefix implies read-only, but nothing beyond that is disclosed.

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 concise fragment, roughly ten words, and gets straight to the point. Every word adds signal about the card's contents. It could be improved with a verb and clearer sentence form, but it is appropriately sized for a parameterless tool.

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 an output schema present, the description covers the core payload concept. However, the jargon 'Tier-0' is unexplained, and there is no mention of when the card is available (e.g., market hours, after close) or any fallback behavior. The output schema presumably fills return-value details, but usage context remains thin.

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, and the input schema is an empty object, so schema coverage is trivially 100%. Per calibration, a zero-parameter tool gets a baseline of 4; the description adds clarifying content about what the returned card includes, which is sufficient.

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 names the resource ('Tier-0 morning desk card') and lists its key contents (rails, IV rank, gap, events), making it clear this is a composite daily overview. It is distinct from sibling tools like get_rails or get_iv, though it doesn't explicitly contrast itself. The lack of an explicit verb is a minor gap.

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 gives no guidance on when to use this tool versus alternatives. It implies a morning desk use case but does not state conditions, exclusions, or mention any sibling tool. An agent must infer from the name and context.

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