get_analysis

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

No annotations provided, so description must cover behavioral aspects. It describes the returned content but does not disclose side effects, authentication needs, rate limits, or explicitly state it is read-only. The tool name suggests reading, but not guaranteed.

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?

Single sentence listing many aspects, efficient but run‑on. Could be structured for better readability, but no wasted words.

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?

Has output schema, so description need not repeat return values. However, given the complexity and no parameter semantics, the description is adequate but not fully complete—missing error conditions or prerequisite info.

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 description coverage is 0% and the description does not explain the 'slug' parameter at all. The parameter's purpose, format, or source is not mentioned, leaving the agent without guidance.

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?

Description uses specific verb 'get' and resource 'analysis', and enumerates the content (source firms, inputs, feasibility, method, outputs, etc.), clearly distinguishing from sibling tools like 'list_analyses' which returns a list.

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 explicit when-to-use or alternatives mentioned. It implies use when needing full details of a single analysis, but does not differentiate from tools like 'get_dependencies' or 'get_phase' that return subsets.

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