properties.object_report

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

No annotations are provided. The description implies a read-only operation but does not explicitly confirm no side effects, auth requirements, or error behavior (e.g., if object does not exist).

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. It efficiently states the tool's purpose, though it could be slightly clearer about parameter usage.

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 does not cover the effect of the boolean flags, the return format, or what 'custom props' refers to. For a tool with four parameters and no output schema, this is insufficient for an agent to use it correctly without additional inference.

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%. The description mentions 'data, modifiers, and custom props' but does not explain the boolean parameters (include_data, include_values, include_modifiers) or their defaults, leaving the agent to rely on schema titles alone.

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 specifies a verb ('Report') and a resource ('live RNA properties') and mentions the scope (object, data, modifiers, custom props). However, it does not distinguish itself from sibling tools like 'properties.report'.

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?

No guidance on when to use this tool versus alternatives such as 'properties.report' or 'mesh.report'. The description only states what it does without indicating prerequisites or context.

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