finary_me

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 states 'Does not modify Finary', which is a key behavioral trait for a read operation. It does not mention return format or errors, but for a simple profile read this is acceptable. Adding 'Read' reinforces the non-destructive nature.

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?

Two short sentences, front-loaded with the core action and a clear non-modification statement. No fluff or redundancy. Every word earns its place.

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 zero-parameter, read-only tool, the description covers the essential purpose and side-effect behavior. It does not explicitly state return data format (no output schema exists), but an agent can reasonably infer it returns the profile object. Minor gap, but adequate for this 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?

There are zero parameters, so the baseline is 4. The description does not need to explain parameters because none exist. Schema coverage is 100% vacuously, and no parameter documentation is required.

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 the verb 'Read' with a specific resource, 'authenticated Finary profile', and explicitly states it does not modify. This distinguishes it from sibling tools like finary_transactions or finary_portfolio without ambiguity. The purpose is clear and specific.

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 indicates the tool retrieves the user's own Finary profile, which sets clear context for when it applies. However, it does not explicitly mention alternatives or conditions for when not to use it, though the resource is so distinct that usage is implied. Missing explicit routing to siblings, but adequate.

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