Retrieve a model's parameter expressions, timeline, feature diagnostics, and component structure. For large designs, prefer paginated entity queries to handle data efficiently.
Read parameter expressions, timeline, feature diagnostics and component structure. For large designs prefer paginated entity queries.
| Name | Required | Description | Default |
|---|---|---|---|
| document_id | Yes |
Changes observed during successful MCP inspections.
v0.2.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations provided, the description carries the full burden of behavioral disclosure. It correctly signals a read-only, non-destructive operation and hints that large designs may be expensive by recommending paginated queries. However, it does not describe response shape, limits, or potential errors, so it only partially discloses behavior.
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 with no filler: the first front-loads the tool's scope, and the second provides a practical usage caveat. Every word contributes value, making it an appropriately sized description.
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?
For a single-parameter, read-only overview tool with no output schema, the description covers what data is returned and warns about large designs. It does not explain return formatting or error behavior, but these are relatively minor given the simple input and the provided usage guidance.
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 adds no meaning to document_id beyond the schema's 'Document Id' title. The single parameter is fairly self-explanatory, but the description does not compensate for the missing schema documentation.
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 opens with a strong, specific verb ('Read') and lists four concrete content areas: parameter expressions, timeline, feature diagnostics, and component structure. This clearly distinguishes it from siblings like fusion_inspect and fusion_query_entities, and the final sentence reinforces the differentiation.
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 explicitly advises preferring paginated entity queries for large designs, giving an actionable alternative condition. It does not spell out a broader when-to-use policy, but the enumerated contents imply the appropriate use case clearly enough.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.