get_resident_profile

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

No annotations are provided, so the description carries the burden of disclosing behavior. It adds context by specifying the returned fields, but does not explicitly state authentication requirements, side effects, or error behavior. The word 'Get' implies a read-only operation, but this is not stated explicitly.

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, front-loaded sentence that immediately states the action and resource, followed by a concise list of the returned fields. Every word adds value with no redundancy.

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 no-input getter, the description provides a clear picture of the return content by naming the five fields. It is missing explicit details about the response shape (single object vs array) and error cases, but the absence of an output schema makes this less critical. The description is sufficiently complete for straightforward usage.

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 tool has zero parameters (empty properties object), so there is no parameter semantics to explain. According to the rubric, 0 params yields a baseline of 4. The description adds no parameter information, which is acceptable since none exist.

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's function: 'Get the logged-in resident's profile' and enumerates the specific fields included (name, mobile, email, resident_id, default_flat_occupancy_id). This distinguishes it from sibling tools like get_flat_access or get_occupancy_detail by focusing on the resident's own identity data.

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 usage via the phrase 'logged-in resident', indicating this is for fetching the current user's profile. However, it provides no explicit guidance on when to choose this over alternatives or when not to use it. For example, it doesn't mention that flat-specific data should be retrieved via other getters.

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