fabric_analyze_paper

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

The description gives no behavioral details such as output format, processing steps, or limitations. With no annotations, it fails to disclose any safety or side-effect information.

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?

At one sentence, it is concise but under-specified. It delivers a minimal statement without earning its place through useful details.

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 tool description is incomplete for a tool that presumably performs complex analysis. Without output schema or behavioral notes, it doesn't convey what results to expect or how the analysis works.

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 fully describes the 'input' parameter as 'The input text to process' (100% coverage). The tool description adds no additional parameter guidance, so baseline 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 names the resource type (academic papers/technical documents) but uses the generic verb 'analyze' without specifying the nature of the analysis. It doesn't clearly distinguish from sibling tools like fabric_analyze_claims or fabric_summarize, since 'analyze' could overlap with those.

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 guidance is provided on when to use this tool versus the many sibling analysis tools. The description lacks context about use cases, prerequisites, or alternatives.

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