project_objects_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, yet it only implies read-only semantics via the word 'Read'. It does not say whether the path must point to an open/existing project, what happens on a missing project, or whether the read is scoped to the active session. An output schema exists, so return-value detail is not required, but the operational preconditions are unaddressed.

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?

One compact sentence with the resource list front-loaded and no filler. It is efficient, though the terseness borders on under-specification rather than true conciseness.

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?

With one undocumented required parameter, no annotations, and a crowded set of sibling read tools, the description leaves out both the meaning of 'path' and any disambiguation. The output schema covers return values, but the call-side context an agent needs is largely missing.

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 single required parameter 'path' is never mentioned in the description. The agent cannot tell whether path is a filesystem path to a project file, a project identifier, or an internal object path, so the description fails to compensate for the schema 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 gives a clear verb ('Read') and enumerates the resources returned: objects, part IDs, plates and instance assignments. It is clear what the tool does, but it never distinguishes itself from adjacent readers such as project_geometry_read, project_inspect or native_scene_read, which an agent must choose between.

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 statement of when to use this tool, when not to, or which sibling to pick instead. Given a sibling list containing project_geometry_read, project_painting_read and native_scene_read, the absence of routing guidance leaves selection to guesswork.

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