anon_get_lostfound_item_id

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, openWorld), and the description adds genuinely new behavioral facts: view permission is limited to project members, auth is via the current API key, and the project scope is inferred rather than passed. It does not describe error behavior for missing/nonexistent items.

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?

Three short, front-loaded lines: purpose, permission scope, endpoint plus scoping note. No filler, nothing repeated from structured fields.

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 single-parameter read tool with no output schema and full annotation coverage, the description supplies the access rule, the endpoint shape, and the project-scoping behavior an agent needs to call it correctly. Return payload details are not given, but that is acceptable given 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?

Schema coverage is 0% and the only parameter is a nested path.itemId, so the description must compensate. It does: the REST path template reveals itemId's role and explicitly states projectId is auto-resolved from the API key and must not be passed, preventing a common mistake.

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?

States a specific verb+resource: retrieve a lost-and-found item's detail ('获取失物详情'), which cleanly differs from the sibling list tool anon_get_lostfound and the photo endpoint. It does not explicitly name those siblings to disambiguate, so it stops short of a 5.

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?

Gives access context ('项目成员可查看' – project members can view) but no explicit when-to-use or when-not-to-use guidance relative to anon_get_lostfound or anon_get_lostfound_item_id_photo. Usage is implied rather than directed.

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