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

Annotations already establish that this is a safe, idempotent read operation. The description adds useful behavioral context beyond annotations: the live board updates around 6 AM ET daily, the week scope freezes Thursdays, and the exact returned fields are listed.

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?

Two sentences are front-loaded with the core purpose, followed by scope timing and return fields. There is no wasted text, and the key information appears early.

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?

The description covers purpose, scope behavior, update cadence, and return fields, which is sufficient for a simple read-only ranking tool without an output schema. Its main omission is explicit sibling differentiation, which would help distinguish it from app_rank and movers.

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 coverage is 100%, so the parameters are already documented. The description still adds meaning, especially by clarifying that live is today's blended board with a daily update cadence and week is the latest frozen week with Thursday freezes.

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 clearly states a specific ranked resource: the top n consumer AI apps on Ascension. It is easy to tell what the tool returns, but it does not explicitly distinguish itself from siblings such as app_rank or movers.

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 scope options are explained with concrete timing details, which helps an agent choose between live and week. However, there is no explicit guidance on when to use this tool instead of app_rank or movers.

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