read_curve

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

With no annotations provided, the description carries the full burden of behavioral disclosure. 'Read' implies a non-destructive operation, but the description does not state potential errors, return format, or whether the file must exist. It adds no transparency beyond the verb itself.

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 extremely concise, consisting of a single clear sentence with no wasted words. It is appropriately front-loaded. However, it is arguably under-specified for a full tool description, though the simplicity contributes to its 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?

The description is minimal and lacks essential context. It does not describe the return value, error handling, or how this tool relates to sibling read tools. Given no output schema and no annotations, the description is insufficient for a complete understanding, despite the tool's simplicity.

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 has 100% description coverage, with the parameter 'path' described as 'Path to .tres Curve resource'. The description adds no additional semantics beyond the schema. Baseline of 3 applies because the schema already documents the parameter thoroughly.

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 'Read Curve resource.' clearly states the action (read) and the target resource (Curve), matching the tool name. However, it does not differentiate from sibling tools like read_resource or read_path, which also read resources. It is clear but lacks distinction.

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 is provided on when to use this tool versus alternatives. There is no mention of scenarios, prerequisites, or exclusions. The only implied usage is reading a Curve resource, but this is not explicitly stated as a recommendation or contrasted with other read tools.

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