get_file_composition

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

With no annotations provided, the description carries the full burden of disclosing behavior. It does indicate a read-only operation ('Read') and that it accesses the file directly, which is useful, but it does not describe what the returned 'composition' includes, potential failure modes (e.g., missing file, unsupported format), or whether any session state is affected. This is incomplete for an unannotated tool.

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?

A single, front-loaded sentence with no filler. Every word contributes to the tool's purpose and mechanism. It is appropriately concise for the tool's simplicity.

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?

Although the tool is simple (one parameter, no output schema, no annotations), the description does not fully cover what an agent needs to invoke it confidently. It omits usage guidance, output semantics, and error handling. The phrase 'stored composition' is vague and could mean different things depending on the file system context.

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 schema provides no description for assembly_path (0% coverage), so the description must compensate. The only added meaning is that the path refers to an 'assembly file,' but it does not clarify path format, file type expectations, relative vs absolute paths, or any constraints. This falls short of compensating 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 states a specific verb ('Read'), a resource ('stored composition of an assembly file'), and a distinguishing mechanism ('directly from the file itself'). This makes it clear the tool reads from the file rather than the in-memory document, which differentiates it from the sibling get_document_composition. However, it does not explicitly name any sibling, so it lacks full 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?

There is no guidance on when to use this tool versus alternatives like get_document_composition or scan_model_files. No conditions, exclusions, or alternative tools are mentioned, leaving the agent to infer context from the name and description alone.

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