property_read

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

Description is minimal and with no annotations, fails to disclose behavioral traits such as side effects (none expected), prerequisites (e.g., note must exist), or error handling. The agent cannot determine behavior beyond the name.

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 concise sentence, but it sacrifices necessary detail for brevity. It earns its place but is borderline under-specified.

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 4 parameters, no output schema, and no annotations, the description provides insufficient context. It does not explain how to identify the note, what a property value is, or what the return format looks like.

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 low (25%), and the description adds no parameter meaning. The required 'name' parameter and optional 'file', 'path', 'vault' are unexplained, relying entirely on the schema which lacks descriptions for three parameters.

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 clearly states the tool reads a property value from a note, using a specific verb and resource. It distinguishes from sibling tools like 'properties' (list) and 'read' (content). However, it does not explicitly tie the purpose to the parameters.

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 like 'properties' or 'read'. No exclusions or context provided, leaving the agent to infer appropriate usage.

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