get_last_modified_prims

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

No annotations are provided, and the description only gives a high-level action. It doesn't disclose what 'recently modified' means, whether the operation is read-only, or if there are any side effects, leaving behavioral details opaque.

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?

The description is a single sentence with no redundant information, making it very concise and to the point.

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 description lacks essential context such as the meaning of 'edit target layer,' the behavior of the count parameter, and what the returned prims contain. For a tool with no annotations and no output schema, this is insufficient for an agent to predict behavior.

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 defines 'path' and 'count' with no descriptions, and the tool description does not explain their purpose or format. With 0% schema description coverage, this is a complete gap.

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 uses a specific verb 'Get' with a focused resource 'recently modified prims' and scoping to 'the edit target layer,' clearly distinguishing it from generic prim access tools like get_prims.

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 states what it does but provides no guidance on when to use it over other tools (e.g., get_prims) or any exclusions. The use case is implied but not explicit.

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