Get portfolio

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

No annotations provided. The description only states the HTTP method (GET), implying read-only, but fails to disclose any other behavioral traits such as authentication needs, rate limits, or idempotency.

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 very short but repeats 'Get portfolio' from the title. It includes HTTP method and tags, which are partially redundant. Could be more concise by removing duplication.

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 large set of sibling tools, especially 'weeek_get_portfolios', the description does not differentiate. No output schema means the description should hint at return format, but it does not.

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 0%. The description adds no meaning to the 'id' parameter beyond what the schema provides (required, string or number). Does not explain what the ID represents.

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 states 'Get portfolio' and the HTTP method/URL, clearly indicating the resource and action. However, it does not differentiate from sibling 'weeek_get_portfolios' which likely returns all portfolios.

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?

No explicit guidance on when to use this tool versus alternatives. The name implies it retrieves a single portfolio by ID, but without context to contrast with listing or other retrieval tools.

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