project_geometry_read

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

No annotations are provided, so the description carries the full behavioral burden. 'Inspect' implies a read, but it never states that the operation is non-mutating, what happens with an invalid path/member, or that limit/offset imply pagination. That is a significant gap for a 4-parameter tool with zero annotation coverage.

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, so it is appropriately sized. It is concise to the point of under-specification, but the structure itself is efficient.

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?

An output schema exists, so return values need not be explained, but the description is incomplete regarding parameter meaning, pagination behavior, and selection relative to siblings. For a tool with four bare-named parameters, it should say more.

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%, so the description must compensate for four undocumented parameters. It only hints at what a 'member' means (a 3MF member file); it says nothing about 'path', 'limit', or 'offset', including that the latter two are pagination controls with defaults.

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?

States a specific verb ('Inspect') and a concrete set of resources (mesh IDs, component references, build transforms) scoped to a 3MF member. It is clear what the tool reads, but it doesn't differentiate itself from nearby siblings like mesh_inspect or project_objects_read.

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 choose this over mesh_inspect, project_objects_read, or native_scene_read, nor any prerequisites or exclusions. The agent must infer usage from the name alone.

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