get_rent_status

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

No annotations are provided, so the description carries the burden. It explicitly discloses 'Read-only' and 'scoped to the authenticated user's properties,' which are key behavioral and authorization traits. It does not describe return format or edge cases, but for a read operation this is reasonably transparent.

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 two sentences, front-loaded with the action and resource, and contains no filler. Every clause adds value: 'Read rent-payment status for a property over a given period' states purpose, and 'Read-only, scoped to the authenticated user's properties' adds constraints.

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?

Given the simplicity of the tool and the absence of an output schema, the description covers the essential context: what it does, scope, and read-only nature. It does not elaborate on the content of the status response, but the core selection and invocation needs are addressed.

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%, but the description adds meaning to 'property_id' and 'period' by mentioning 'property' and 'a given period.' 'oauth_token' is self-explanatory. This partially compensates for the lack of schema descriptions, but period format and property identification details remain unspecified.

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 specific verb ('Read') and resource ('rent-payment status') and clearly scopes it to a property and period. It distinguishes itself from sibling tools like generate_lease and notify_tax_authority, which have different purposes.

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 states 'Read-only, scoped to the authenticated user's properties,' which provides clear context on when to use it (for read-only queries) and its authorization scope. It does not explicitly name alternatives but the distinction from siblings is obvious.

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