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

With no annotations provided, the description carries the full burden. It states 'Returns data, not recommendations -- interpret results yourself', disclosing that it provides raw data rather than advice. It also lists included components (market regime, signals, anomalies, etc.), which sets expectations. However, it does not mention any side effects or limitations like rate limits, so it's slightly incomplete.

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 concise, using bold for emphasis and front-loading the purpose. Every sentence contributes value without redundancy. It efficiently communicates the tool's role, usage guidance, and output nature in just a few sentences.

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 complexity of the tool (aggregates multiple data sources) and the absence of an output schema, the description provides a good overview of what data is included. However, it lacks details on the output structure or format, which would help an agent parse the response. Still, it is mostly complete for making an informed choice.

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 schema already describes both parameters well. The description reinforces their use (e.g., 'Omit for full ecosystem view' for 'focus' and the meaning of 'morning' vs 'weekly' for 'timeframe') but adds little beyond what the schema provides. A baseline of 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 clearly identifies the tool as an 'All-in-one ECOSYSTEM briefing' that aggregates multiple data points (market regime, signals, anomalies, etc.). It distinguishes itself from the sibling tool tokenintel_token_context by specifying 'use tokenintel_token_context for a SINGLE-TOKEN deep dive', making the purpose specific and differentiated.

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?

Explicit usage guidance is provided: 'USE THIS for a market-wide overview' and 'USE tokenintel_token_context for a SINGLE-TOKEN deep dive'. It also suggests replacing sequential calls to 6+ tools, giving clear context on when to apply this tool over alternatives.

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