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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It states 'Returns' which implies a read-only operation, but it does not mention response format, pagination, whether it returns a list or single item, authentication needs, or any side effects. For a tool with no output schema, this lack of return-structure detail is a significant gap.

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 sentence that front-loads the main action ('Returns Stack Signal') and adds a concise explanatory clause in the em-dash. There is no fluff or redundancy. It is appropriately sized and easy to parse.

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?

With 3 optional parameters, no output schema, and no annotations, the description should clarify the return structure and behavior. It only vaguely indicates the content ('market intelligence with commentary') but doesn't explain whether the response is a list, how pagination works, or what fields are included. This leaves the agent uncertain about how to handle the result, especially without an output schema.

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 input schema covers 100% of parameters with individual descriptions for limit, offset, and category, so the baseline is 3. The tool description does not add any parameter context, but it is not necessary given the complete schema. The description also doesn't mention defaults, but those are documented in the schema.

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 the tool returns 'Stack Signal' and describes it as curated precious metals market intelligence with commentary. This specifies the verb and resource clearly, though it does not explicitly differentiate from sibling tools like get_daily_brief or get_speculation, which might also return market-related content. The title and name reinforce the 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?

The description does not provide any guidance on when to use this tool versus alternatives. There are no stated conditions, prerequisites, or exclusions. Without mentioning sibling tools or contextual cues, the agent receives no help in deciding between this and similar retrieval tools like get_daily_brief.

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