Inspect Micro records

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and destuctiveHint=false, so the safety profile is covered. The description adds meaningful context by noting records are 'latest', 'bounded', and tied to the owner project, plus a data-sensitivity warning about not copying values into prompts unless required.

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 compact: two sentences with the core action front-loaded. The second sentence earns its place by adding a security/data-handling instruction, so there is no meaningful fluff.

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?

For a simple one-parameter read-only tool with an output schema and readOnly/openWorld/idempotent annotations, the description is largely sufficient. The term 'bounded' is slightly vague, but the tool's scope and data-handling expectations are conveyed clearly enough for an agent to call it correctly.

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 100%, so the path parameter is already documented in the schema. The description does not add much parameter-level detail beyond tying the records to the linked owner project, which aligns with the schema baseline.

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 clear verb ('Read') and identifies the resource ('latest bounded project records for the linked owner project'). It does not explicitly differentiate itself from sibling tools like micro_logs or micro_record_delete, but its read-only nature is unambiguous.

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 implies this tool should be used when the agent needs to read the latest bounded project records, and the instruction to treat values as user data gives some handling guidance. However, it does not explicitly state when to prefer this over alternatives or mention any exclusions.

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